December 26, 2013 at 8:23 pm
Do i need to Add the SYSTEM Databases the .mdf of ( Master, msdb, temp etc) to the Storage? please help me thank you masters
December 27, 2013 at 7:29 am
Not sure exactly what you are asking. Are you moving data from internal drives to a SAN? Is the server clustered or a standalone install? What version of SQL Server?
December 29, 2013 at 1:40 pm
niver (12/26/2013)
Do i need to Add the SYSTEM Databases the .mdf of ( Master, msdb, temp etc) to the Storage? please help me thank you masters
You can move all paths to the SAN storage if you wish, just ensure you update any path dependencies within sql srever.
For example log path locations for sql agent jobs, etc and the full text default location
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
January 2, 2014 at 5:25 am
If you want the redundant storage that a SAN gives you, yes. If you want faster performance for the system databases, you might consider local storage. Everything is a tradeoff.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 2, 2014 at 5:42 am
Grant Fritchey (1/2/2014)
If you want faster performance for the system databases, you might consider local storage.
Unless its an FCI then you are required to use shared storage not local
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
January 2, 2014 at 5:53 am
Perry Whittle (1/2/2014)
Grant Fritchey (1/2/2014)
If you want faster performance for the system databases, you might consider local storage.Unless its an FCI then you are required to use shared storage not local
100% true. But, you probably wouldn't be asking about where to put storage if you had no choice in the matter.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 2, 2014 at 7:07 am
Grant Fritchey (1/2/2014)
100% true. But, you probably wouldn't be asking about where to put storage if you had no choice in the matter.
Sure, about the only time is when migrating data between LUNs
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
January 2, 2014 at 11:51 pm
yes it is a FC connection, but what im looking for is an implementation that all the sysdatabases and production databases is located to the SAN and what is the advantages and disadvages thank you very much
January 3, 2014 at 12:14 am
I store them on local drives and make sure they are backed up each night. Keeping them on a local drive, other than the OS drive is still better.
Thanks
chandan
January 3, 2014 at 1:04 am
niver (1/2/2014)
yes it is a FC connection, but what im looking for is an implementation that all the sysdatabases and production databases is located to the SAN and what is the advantages and disadvages thank you very much
Its perfectly viable to use consolidated\shared storage, certainly makes storage management easier.
Having the system databases on local disk means that if you lose the San sql will likely stay online but then what good is this if you have lost all user dbs?
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply