SQL Server DBA and Azure SQL Insights

1. Check whether the Backup is valid or not Restore verifyonly from disk = ‘Backup path’

2. We will check the Base Backup is restored first or not

3. Check the LSN sequence 4. Check user has required permissions

5. Check the disk space

6. We will check basing upon the error message.

1. SCM – start instance (run: sqlservermanager.msc)

2. OS services (run: services.msc)

3. SAC – Surface Area Configuration (2005)

4. On the command line: Run – net start service name Find the service name in services.msc

5. Using object explorer (Right click on the instance and try to start)

6. Startup parameters have incorrect file path locations. Right click the instance -> Properties -> General Tab -> startup parameters

7. Need to check whether Services are disabled or not Services.msc

8. We will check basing upon the error message

1. Check the log file size by using DBCC sqlperf(logspace), we can increase log size up to 2TB.

2. Purging the old files.

3. Take a Log Backup if database in full recovery model i. Backup log dbname to disk =’path’

4. Run the checkpoint if database in simple recovery model.

5. Increase the LOG file size or Enable Auto Growth (Make sure it’s not set to Maximum).

6. Add one more T-Log file from another drive.

7. Shrink the file Use dbname Go DBCC shrinkfile (<transactionlogname>,1).

8. Request windows team to add more space.

9. If the recovery model is Full change to Simple 10. Find the long running transactions and kill after approval.

Pages