June 16, 2009 at 11:57 am
I'm looking for some best practices and also how other dba's implement names instances. We are running 3 SQL Server Standard editions with the default instance only. All three of these servers are connected to a NAS - IBM N 6040.
Question 1: how often do you backup the systems databases?
Questions 2: I just got a request to install a named instance into our production environment. Does anybody have a Best Practice or any words of advice. Also what gotcha's I can look out for?
Thanks!
June 16, 2009 at 12:05 pm
Question 1: how often do you backup the systems databases?
Generally once a week is sufficient. Also you may want to script out ur logins whenever u create/delete/modify any login; also your jobs.f
Questions 2: I just got a request to install a named instance into our production environment. Does anybody have a Best Practice or any words of advice. Also what gotcha's I can look out for?
Thanks!
I guess there is not much difference in how you plan default or named instance as it is a complete new server installation altogether.
June 16, 2009 at 12:08 pm
I back up system databases daily. Should probably only do it when they change, but I'm too lazy to keep track of that, so they get backed up daily. Old backups go onto tape and are kept off-site. Last 2 backups (today and yesterday) are on disk, and yesterday's is on tape and taken off-site at the end of today.
The main thing with instancing SQL Server is resource management. You need to make sure they play nice together when it comes to RAM is the main thing, in my limited experience with multiple instances on the same server. (I'm more accustomed to virtual servers, which manage that for you.)
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
June 16, 2009 at 1:00 pm
I agree.
We put off our second instance installation, when i analyzed our resouces.
I was at 4GB RAM+SQL Standard 2005/SAN/Quad Core.
The First instance had 55 DB's+SSAS+SSIS+SSRS.. so it was a BIG NO.
We moved from 4GB to 8GB+2 socket (4 cores each=total 8 cores)+SQLStd edition2005+windows 2003 Enterprise Edition (to support the extended memory)+SAN(as before)
Now we have 2 instances runing at optimal efficency.
Check that your Hardware resources to see if they are optimal to support the instance(s) of SQL server.
Maninder
www.dbanation.com
June 16, 2009 at 1:12 pm
If you have the space just backup the system databases when you backup the user databases, that is what I have done. This gives you a snapshot of the databases within the same timeframe.
With adding an instance you will need to re-run the service pack installation to patch the additional instances. I would get a good backup of the SQL server, OS and all, just in case:-D
Shawn Melton
Twitter: @wsmelton
Blog: wsmelton.github.com
Github: wsmelton
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply