make sure to import all the rollover trace files – and then it will be enabled you can also try closing and reopening profiler

In SSMS you can select a SQL Agent job, right click and script it as a CREATE. That will give you a script that you can run on another server to create the same job.

use master go declare @databaseName varchar(50), @backupFileName varchar(100), @restoreDirectory varchar(100) — Set the name of the database to restore set @databaseName = ‘database’ — Set the path to the directory containing the database backup set @restoreDirectory = ‘pathBackupsfolder’ — Create the backup file name based…

use master go declare @databaseName varchar(50), @backupFileName varchar(100), @restoreDirectory varchar(100) — Set the name of the database to restore set @databaseName = ‘database’ — Set the path to the directory containing the database backup set @restoreDirectory = ‘pathBackupsLogsfolder’ — Create the backup file name based…

NORECOVERY: Tells SQL Server that you are not finished restoring the database and that subsequent restore files will occur. While the database is in this state, the database is not yet available, so no connections are allowed. RECOVERY: Tells SQL Server that you are finished…

run this sql: RESTORE DATABASE  databasename  WITH RECOVERY

my maintenance plan for defrag-ing indexes was failing due to a disabled index ran this to re-enable index: ALTER INDEX [indexname] ON dbname.tablename REBUILD GO

open SSMS – right click on the Server – Properties – Database Settings – Database Default Locations good idea to not have your databases on the c drive