SQL Server Performance Forum – Threads Archive

Identical Test and Production

Environment: Win2k3, SQL2k SP3
What is the best practice to be assure that from software point of view, my Test server is identical to Production? I want to focus on SQL Server and Windows settings. Is there a checklist?
CanadaDBA

---

I think you want to use Replication
Refer Books On Line and this site
http://vyaskn.tripod.com/repl_ques.htm Madhivanan Failing to plan is Planning to fail

---

No, I am not going to replicate. I just want to ensure that my Test and Production SQL Server settings are the same. CanadaDBA

---

And easy way:
run sp_configure in both servers, print and compare. Is no too long.
Luis Martin
Moderator
SQL-Server-Performance.com One of the symptoms of an approaching nervous breakdown is the belief that one’s work is terribly important
Bertrand Russell
All postings are provided “AS IS” with no warranties for accuracy.

---

Is that all I have to do? I can’t believe it. It’s amazing, Luis!
CanadaDBA

---

hi, you can do one more thing. Try to use SQLDIAG.exe which may give you all info related to your System, OS, and SQL Server along with Hardware related, even about ur RAID Controllers. You will get the utility in
%rogram FilesMicrosoft SQL ServerMSSQLBinn If you are using SP4, then you have some workaround to use this.
You have to use SQLDIAG.exe which is available in SP3a, copy and replace with the current one in the folder. This will give you a log file which will be in the LOG folder. using this, you can compare both systems. -Johnson

---

Yes, to compare both SQL configuration, sp_configure is easier.
Luis Martin
Moderator
SQL-Server-Performance.com One of the symptoms of an approaching nervous breakdown is the belief that one’s work is terribly important
Bertrand Russell
All postings are provided “AS IS” with no warranties for accuracy.

---

Great information! Thank you folks![8D][<img src=’/community/emoticons/emotion-1.gif’ alt=’‘ />][^]<br /><br />CanadaDBA

---

It’s not all THAT amazing – you run those commands to see the settings, then manually check for any differences, and make the necessary changes manually …

---

Oh! Of course I have to take action after the comparison. But I was amazed about using the sp_Configure. I’d never thought about this kind of usage. Also, the SQLDiag.exe seems very useful and I am going to test it as well. Thanks for following the posts and sending your hints.
CanadaDBA

---

SQLDIAG has been included from SP2 onwards (I think) and it must be run on a weekly basis say during monday eary hours to get configuration and information about the SQL Server. It also helps to ascertain information for MS PSS in few cases and they recommend it too. WE do have this tool on all of our SQL Servers (600) without a single point of failure. Satya SKJ
Contributing Editor & Forums Moderator
http://www.SQL-Server-Performance.Com
This posting is provided “AS IS” with no rights for the sake of knowledge sharing.

---

Hey Satya,
It seems it is very important and as you have mentioned it is a "must". May be I should ask after I ran the utility at least once but what you are looking for by running it?
Thanks,
CanadaDBA

---

http://msdn.microsoft.com/library/en-us/coprompt/cp_sqldiag_96k9.asp
http://searchsqlserver.techtarget.com/general/0,295582,sid87_gci1115601,00.html Check the contents of the output and come with yoru doubts.
fyi. Satya SKJ
Contributing Editor & Forums Moderator
http://www.SQL-Server-Performance.Com
This posting is provided “AS IS” with no rights for the sake of knowledge sharing.

---

]]>