Database With Fun (While 1 = 1)

Central Management Server If you read up on this, it talks about setting up groups of servers, necessary if you’re managing QA differently than production. It also has scripting against multiple servers, another great thing. Finally it lets you evaluate policies against multiple servers. Cool. It sounds perfect. Let’s explore. Setting up the Central Management Server Creating a Central Management Server (CMS) is pretty easy, though it does have to be on SQL Server 2008 or better. You also can’t make the CMS server one of your managed servers. Other than that, just pick a machine and go to the Registered Servers window in SSMS by clicking “ View -> Registered servers ” in the menus. Right there in the registered server tree on the left is a folder called “ Central Management Servers ” (and yes, you can set up more than one, or set up Management Servers for your Management Server, or…). Right-click on that folder and select “ Register Central Management Server ” from the contex...

Retrieving backup information We’re going to look at three different commands:  LABELONLY ,  HEADERONLY ,  FILELISTONLY . These three read the information stored about the backup in the backup file and display it all for you. LABELONLY RESTORE LABELONLY FROM DISK   =   'd:\bu\mm.bak'  ; The ouptut from my backup file is as follows: MediaName NULL MediaSetId C78024B4-4FD7-4141-98F4-685C8B127B14 FamilyCount 1 FamilySequenceNumber 1 MediaFamilyId B61166AA-0000-0000-0000-000000000000 MediaSequenceNumber 1 MediaLabelPresent 0 MediaDescription NULL SoftwareName Microsoft SQL Server SoftwareVendorId 4608 MediaDate 2012-02-01 14:31:09.000 MirrorCount 1 IsCompressed 0 HEADERONLY The amount of information you get when you read the entire header is fairly insane. You retrieve it the same way as you would retrieve the  LABELONLY  data: RESTORE HEADERONLY FROM DISK   =   'd:\bu\mm.bak'  ; This command outpu...

A number of problems can prevent the SQL Server service from starting- Service account password incorrect or account locked or disabled Corrupt or missing master database files Corrupt or missing model database files Unable to create  tempDB Unable to open the error log this is the error thats faced initially- The first place you should start looking for the cause is the SQL Server error log. The SQL error log is just a text file on disk. If you're unsure of its location, check the startup parameters of the SQL Server service in SQL Server Configuration Manager. " C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Log\ " Incorrect password or service account locked or disabled I've seen this happen when the administrator has configured the SQL Server service account to require regular password changes, and also in cases where DBAs or developers know the SQL Server service account password and sometimes use it, often to a...