Good morning to everyone!
I have a 3Gig SQL database that currently has all Indexes, Logs, and Data on one drive. We have a new server that will be put in place on Wednesday and thankfully we will be putting the Indexes and TransLogs on different drives from the actual Data. Does anyone have a recommendation on his/her preferred way of doing this and what are some of the advantages/disadvantages some of you may have encountered? This isn't homework. I am finally getting the hang of manipulating and working with our database and will need to accomplish the server switch in about two weeks. Or if you have a recommended reading on this - please point me to it and I'll get to practicing!
Thanks to everyone!
Tiffanieput indices on different drives than the data. you can create seperate filegroups and put indices for one set of tables on one drive and data on the other and do the vice versa for another set of tales. put T-Logs on a completely seperate drive from the data and indices. I do not want to start the RAID debate.|||Thanks Sean,
We are putting everything on their own drives, but I was wondering how everyone goes about pointing the tables to the new locations of the I&Ts? No raid discussion from me - server is already built I just get to play with moving everything and making sure it works. Basically we're planning to fully backup on the old server and restore on the new. Somehow I need to adjust the paths though?
Tiffanie|||Monday... erased.|||tables that are frequently joined, you might to keep oon seperate filegroups.
I do not think you can use ALTER TABLE to change filegroups.
I am not sure you are going tobe able to do a backup and restore. You may have to script your whole database in the EM (easy to do). and adjust your create table statements with ON PRIMARY or SECONDARY etc... specified. Then you will have to move the data over without using a backup.
The indices are easy. Just drop and recreate. You can use the EM or write some code that writes some code against sysindexes to do the job.|||Thanks Sean - I'll play around with that.
Have a terrific day!
Tiffanie
Showing posts with label logs. Show all posts
Showing posts with label logs. Show all posts
Friday, March 30, 2012
Wednesday, March 21, 2012
Move transaction logs in SQL cluster
Hi
I need to move the transaction logs for all the sql db's (including master,
model and user db's etc) to a seperate drive. Does anyone have any experience
doing this in a sql cluster?
Thanks
Parky
Parky wrote:
> Hi
> I need to move the transaction logs for all the sql db's (including
> master, model and user db's etc) to a seperate drive. Does anyone
> have any experience doing this in a sql cluster?
There is no difference if you move t-log in a single box machine or in a
cluster environment.
You have to pay attention to move db files ONLY on shared disk and modify,
using EM, the switch -l in startup properties of SQL Server and assign them
the new location of t-log of master database
> Thanks
Bye
Luca Bianchi
Microsoft MVP - SQL Server
http://mvp.support.microsoft.com
http://italy.mvps.org
|||Hello Parky,
I agree with Luca. There is no difference between moving the db files on a standalone SQL server v/s clustered SQL Server. One difference is that the shared dirve where you want to move the db files should be in
the dependency list of SQL Server resource. (For Ex. Say you want to move the Tlogs to a shared drive F:. Make sure that SQL Server resource has F: as a dependency. If not you will have have make it. Note that
this requires a downtime as you will have to take SQL Server resource offline, add the shared drive as a dependency and then take SQL Server online. Then you can use your usual steps (see
http://support.microsoft.com/kb/224071/EN-US/
INF: Moving SQL Server Databases to a New Location using Detach/Attach )
If you have never done this on a cluster, I will recommend you to practice the steps on a test SQL Cluster or a cluster using virtual technology.
HTH,
Best Regards,
Uttam Parui
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx
|||I would leave the System databases and there log file on one drive and split
the user databases to two diffrent databases, that way is you losse the log
drive you can still get sql server running and manage it to recreate the user
databases from the datafiles with diffrent location of the log files.
"Uttam Parui[MS]" wrote:
> Hello Parky,
> I agree with Luca. There is no difference between moving the db files on a standalone SQL server v/s clustered SQL Server. One difference is that the shared dirve where you want to move the db files should be in
> the dependency list of SQL Server resource. (For Ex. Say you want to move the Tlogs to a shared drive F:. Make sure that SQL Server resource has F: as a dependency. If not you will have have make it. Note that
> this requires a downtime as you will have to take SQL Server resource offline, add the shared drive as a dependency and then take SQL Server online. Then you can use your usual steps (see
> http://support.microsoft.com/kb/224071/EN-US/
> INF: Moving SQL Server Databases to a New Location using Detach/Attach )
> If you have never done this on a cluster, I will recommend you to practice the steps on a test SQL Cluster or a cluster using virtual technology.
> HTH,
> Best Regards,
> Uttam Parui
> Microsoft Corporation
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security.
> Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites:
> http://www.microsoft.com/protect
> http://www.microsoft.com/security/guidance/default.mspx
>
>
I need to move the transaction logs for all the sql db's (including master,
model and user db's etc) to a seperate drive. Does anyone have any experience
doing this in a sql cluster?
Thanks
Parky
Parky wrote:
> Hi
> I need to move the transaction logs for all the sql db's (including
> master, model and user db's etc) to a seperate drive. Does anyone
> have any experience doing this in a sql cluster?
There is no difference if you move t-log in a single box machine or in a
cluster environment.
You have to pay attention to move db files ONLY on shared disk and modify,
using EM, the switch -l in startup properties of SQL Server and assign them
the new location of t-log of master database
> Thanks
Bye
Luca Bianchi
Microsoft MVP - SQL Server
http://mvp.support.microsoft.com
http://italy.mvps.org
|||Hello Parky,
I agree with Luca. There is no difference between moving the db files on a standalone SQL server v/s clustered SQL Server. One difference is that the shared dirve where you want to move the db files should be in
the dependency list of SQL Server resource. (For Ex. Say you want to move the Tlogs to a shared drive F:. Make sure that SQL Server resource has F: as a dependency. If not you will have have make it. Note that
this requires a downtime as you will have to take SQL Server resource offline, add the shared drive as a dependency and then take SQL Server online. Then you can use your usual steps (see
http://support.microsoft.com/kb/224071/EN-US/
INF: Moving SQL Server Databases to a New Location using Detach/Attach )
If you have never done this on a cluster, I will recommend you to practice the steps on a test SQL Cluster or a cluster using virtual technology.
HTH,
Best Regards,
Uttam Parui
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx
|||I would leave the System databases and there log file on one drive and split
the user databases to two diffrent databases, that way is you losse the log
drive you can still get sql server running and manage it to recreate the user
databases from the datafiles with diffrent location of the log files.
"Uttam Parui[MS]" wrote:
> Hello Parky,
> I agree with Luca. There is no difference between moving the db files on a standalone SQL server v/s clustered SQL Server. One difference is that the shared dirve where you want to move the db files should be in
> the dependency list of SQL Server resource. (For Ex. Say you want to move the Tlogs to a shared drive F:. Make sure that SQL Server resource has F: as a dependency. If not you will have have make it. Note that
> this requires a downtime as you will have to take SQL Server resource offline, add the shared drive as a dependency and then take SQL Server online. Then you can use your usual steps (see
> http://support.microsoft.com/kb/224071/EN-US/
> INF: Moving SQL Server Databases to a New Location using Detach/Attach )
> If you have never done this on a cluster, I will recommend you to practice the steps on a test SQL Cluster or a cluster using virtual technology.
> HTH,
> Best Regards,
> Uttam Parui
> Microsoft Corporation
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security.
> Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites:
> http://www.microsoft.com/protect
> http://www.microsoft.com/security/guidance/default.mspx
>
>
Move Temp DB and Logs to get more speed?
We are running a server with IIS and SQL 2K using the following
configuration:
C: OS/Inetpub
D: SQL 2K DB/Logs
E: IIS Logs
F: Not Used
G: Not Used
We have a single SQL 2K DB that all the websites use.
I'm currently constrained to a single server and the drive configuration. I
would like to optimize better by using the new F: and G: drives.
Additionally the C: and D: have no problem keeping up so I could move IIS
logs to the C: drive if needed.
Based on reading I've been doing it sounds like I will get the best
performance from moving the TempDB and the Logs files to different drives
but which configuration would be best:
F: TempDB DB and Logs
G: Our main DB Log Files
or
F: TempDB Logs
G: Our main DB Log Files
or
Something else.
Please suggest my best route.
Thanks!
It's a best practice to have the data and logs on separate partitions. This
is both for safety (High Availability) as well as performance. Also, try to
keep tempdb separate from your app DB's. Thus, you could go with:
D: app data
F: app log
G: tempdb
Try that first. You can also move the tempdb log to F: and see if that
improves or degrades performance. Logs should not be placed on RAID5
partitions.
HTH
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"Bishop" <nospam@.nospam.com> wrote in message
news:u20v0S7gIHA.4692@.TK2MSFTNGP05.phx.gbl...
We are running a server with IIS and SQL 2K using the following
configuration:
C: OS/Inetpub
D: SQL 2K DB/Logs
E: IIS Logs
F: Not Used
G: Not Used
We have a single SQL 2K DB that all the websites use.
I'm currently constrained to a single server and the drive configuration. I
would like to optimize better by using the new F: and G: drives.
Additionally the C: and D: have no problem keeping up so I could move IIS
logs to the C: drive if needed.
Based on reading I've been doing it sounds like I will get the best
performance from moving the TempDB and the Logs files to different drives
but which configuration would be best:
F: TempDB DB and Logs
G: Our main DB Log Files
or
F: TempDB Logs
G: Our main DB Log Files
or
Something else.
Please suggest my best route.
Thanks!
|||Hi Tom, thanks for the advice, just to clarify are you suggesting moving
both TempDB Data and Log to G to start or just the Data?
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:Ogjz5b7gIHA.5208@.TK2MSFTNGP04.phx.gbl...
> It's a best practice to have the data and logs on separate partitions.
> This
> is both for safety (High Availability) as well as performance. Also, try
> to
> keep tempdb separate from your app DB's. Thus, you could go with:
> D: app data
> F: app log
> G: tempdb
> Try that first. You can also move the tempdb log to F: and see if that
> improves or degrades performance. Logs should not be placed on RAID5
> partitions.
> HTH
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "Bishop" <nospam@.nospam.com> wrote in message
> news:u20v0S7gIHA.4692@.TK2MSFTNGP05.phx.gbl...
> We are running a server with IIS and SQL 2K using the following
> configuration:
> C: OS/Inetpub
> D: SQL 2K DB/Logs
> E: IIS Logs
> F: Not Used
> G: Not Used
> We have a single SQL 2K DB that all the websites use.
> I'm currently constrained to a single server and the drive configuration.
> I
> would like to optimize better by using the new F: and G: drives.
> Additionally the C: and D: have no problem keeping up so I could move IIS
> logs to the C: drive if needed.
> Based on reading I've been doing it sounds like I will get the best
> performance from moving the TempDB and the Logs files to different drives
> but which configuration would be best:
> F: TempDB DB and Logs
> G: Our main DB Log Files
> or
> F: TempDB Logs
> G: Our main DB Log Files
> or
> Something else.
> Please suggest my best route.
> Thanks!
>
>
|||Initially, try both data and log for tempdb. If that is satisfactory, you
can leave it. If you still have perf issues, then move the log to another
drive.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"Bishop" <nospam@.nospam.com> wrote in message
news:OJ8syj7gIHA.5752@.TK2MSFTNGP03.phx.gbl...
Hi Tom, thanks for the advice, just to clarify are you suggesting moving
both TempDB Data and Log to G to start or just the Data?
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:Ogjz5b7gIHA.5208@.TK2MSFTNGP04.phx.gbl...
> It's a best practice to have the data and logs on separate partitions.
> This
> is both for safety (High Availability) as well as performance. Also, try
> to
> keep tempdb separate from your app DB's. Thus, you could go with:
> D: app data
> F: app log
> G: tempdb
> Try that first. You can also move the tempdb log to F: and see if that
> improves or degrades performance. Logs should not be placed on RAID5
> partitions.
> HTH
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "Bishop" <nospam@.nospam.com> wrote in message
> news:u20v0S7gIHA.4692@.TK2MSFTNGP05.phx.gbl...
> We are running a server with IIS and SQL 2K using the following
> configuration:
> C: OS/Inetpub
> D: SQL 2K DB/Logs
> E: IIS Logs
> F: Not Used
> G: Not Used
> We have a single SQL 2K DB that all the websites use.
> I'm currently constrained to a single server and the drive configuration.
> I
> would like to optimize better by using the new F: and G: drives.
> Additionally the C: and D: have no problem keeping up so I could move IIS
> logs to the C: drive if needed.
> Based on reading I've been doing it sounds like I will get the best
> performance from moving the TempDB and the Logs files to different drives
> but which configuration would be best:
> F: TempDB DB and Logs
> G: Our main DB Log Files
> or
> F: TempDB Logs
> G: Our main DB Log Files
> or
> Something else.
> Please suggest my best route.
> Thanks!
>
>
|||Changes worked great! Thanks for the recomendations.
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:%234W8TpKhIHA.6032@.TK2MSFTNGP03.phx.gbl...
> Initially, try both data and log for tempdb. If that is satisfactory, you
> can leave it. If you still have perf issues, then move the log to another
> drive.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "Bishop" <nospam@.nospam.com> wrote in message
> news:OJ8syj7gIHA.5752@.TK2MSFTNGP03.phx.gbl...
> Hi Tom, thanks for the advice, just to clarify are you suggesting moving
> both TempDB Data and Log to G to start or just the Data?
> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
> news:Ogjz5b7gIHA.5208@.TK2MSFTNGP04.phx.gbl...
>
|||Great news. Thanx for the follow-up. :-)
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"Bishop" <nospam@.nospam.com> wrote in message
news:uDeCmGTiIHA.1164@.TK2MSFTNGP02.phx.gbl...
Changes worked great! Thanks for the recomendations.
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:%234W8TpKhIHA.6032@.TK2MSFTNGP03.phx.gbl...
> Initially, try both data and log for tempdb. If that is satisfactory, you
> can leave it. If you still have perf issues, then move the log to another
> drive.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "Bishop" <nospam@.nospam.com> wrote in message
> news:OJ8syj7gIHA.5752@.TK2MSFTNGP03.phx.gbl...
> Hi Tom, thanks for the advice, just to clarify are you suggesting moving
> both TempDB Data and Log to G to start or just the Data?
> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
> news:Ogjz5b7gIHA.5208@.TK2MSFTNGP04.phx.gbl...
>
configuration:
C: OS/Inetpub
D: SQL 2K DB/Logs
E: IIS Logs
F: Not Used
G: Not Used
We have a single SQL 2K DB that all the websites use.
I'm currently constrained to a single server and the drive configuration. I
would like to optimize better by using the new F: and G: drives.
Additionally the C: and D: have no problem keeping up so I could move IIS
logs to the C: drive if needed.
Based on reading I've been doing it sounds like I will get the best
performance from moving the TempDB and the Logs files to different drives
but which configuration would be best:
F: TempDB DB and Logs
G: Our main DB Log Files
or
F: TempDB Logs
G: Our main DB Log Files
or
Something else.
Please suggest my best route.
Thanks!
It's a best practice to have the data and logs on separate partitions. This
is both for safety (High Availability) as well as performance. Also, try to
keep tempdb separate from your app DB's. Thus, you could go with:
D: app data
F: app log
G: tempdb
Try that first. You can also move the tempdb log to F: and see if that
improves or degrades performance. Logs should not be placed on RAID5
partitions.
HTH
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"Bishop" <nospam@.nospam.com> wrote in message
news:u20v0S7gIHA.4692@.TK2MSFTNGP05.phx.gbl...
We are running a server with IIS and SQL 2K using the following
configuration:
C: OS/Inetpub
D: SQL 2K DB/Logs
E: IIS Logs
F: Not Used
G: Not Used
We have a single SQL 2K DB that all the websites use.
I'm currently constrained to a single server and the drive configuration. I
would like to optimize better by using the new F: and G: drives.
Additionally the C: and D: have no problem keeping up so I could move IIS
logs to the C: drive if needed.
Based on reading I've been doing it sounds like I will get the best
performance from moving the TempDB and the Logs files to different drives
but which configuration would be best:
F: TempDB DB and Logs
G: Our main DB Log Files
or
F: TempDB Logs
G: Our main DB Log Files
or
Something else.
Please suggest my best route.
Thanks!
|||Hi Tom, thanks for the advice, just to clarify are you suggesting moving
both TempDB Data and Log to G to start or just the Data?
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:Ogjz5b7gIHA.5208@.TK2MSFTNGP04.phx.gbl...
> It's a best practice to have the data and logs on separate partitions.
> This
> is both for safety (High Availability) as well as performance. Also, try
> to
> keep tempdb separate from your app DB's. Thus, you could go with:
> D: app data
> F: app log
> G: tempdb
> Try that first. You can also move the tempdb log to F: and see if that
> improves or degrades performance. Logs should not be placed on RAID5
> partitions.
> HTH
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "Bishop" <nospam@.nospam.com> wrote in message
> news:u20v0S7gIHA.4692@.TK2MSFTNGP05.phx.gbl...
> We are running a server with IIS and SQL 2K using the following
> configuration:
> C: OS/Inetpub
> D: SQL 2K DB/Logs
> E: IIS Logs
> F: Not Used
> G: Not Used
> We have a single SQL 2K DB that all the websites use.
> I'm currently constrained to a single server and the drive configuration.
> I
> would like to optimize better by using the new F: and G: drives.
> Additionally the C: and D: have no problem keeping up so I could move IIS
> logs to the C: drive if needed.
> Based on reading I've been doing it sounds like I will get the best
> performance from moving the TempDB and the Logs files to different drives
> but which configuration would be best:
> F: TempDB DB and Logs
> G: Our main DB Log Files
> or
> F: TempDB Logs
> G: Our main DB Log Files
> or
> Something else.
> Please suggest my best route.
> Thanks!
>
>
|||Initially, try both data and log for tempdb. If that is satisfactory, you
can leave it. If you still have perf issues, then move the log to another
drive.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"Bishop" <nospam@.nospam.com> wrote in message
news:OJ8syj7gIHA.5752@.TK2MSFTNGP03.phx.gbl...
Hi Tom, thanks for the advice, just to clarify are you suggesting moving
both TempDB Data and Log to G to start or just the Data?
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:Ogjz5b7gIHA.5208@.TK2MSFTNGP04.phx.gbl...
> It's a best practice to have the data and logs on separate partitions.
> This
> is both for safety (High Availability) as well as performance. Also, try
> to
> keep tempdb separate from your app DB's. Thus, you could go with:
> D: app data
> F: app log
> G: tempdb
> Try that first. You can also move the tempdb log to F: and see if that
> improves or degrades performance. Logs should not be placed on RAID5
> partitions.
> HTH
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "Bishop" <nospam@.nospam.com> wrote in message
> news:u20v0S7gIHA.4692@.TK2MSFTNGP05.phx.gbl...
> We are running a server with IIS and SQL 2K using the following
> configuration:
> C: OS/Inetpub
> D: SQL 2K DB/Logs
> E: IIS Logs
> F: Not Used
> G: Not Used
> We have a single SQL 2K DB that all the websites use.
> I'm currently constrained to a single server and the drive configuration.
> I
> would like to optimize better by using the new F: and G: drives.
> Additionally the C: and D: have no problem keeping up so I could move IIS
> logs to the C: drive if needed.
> Based on reading I've been doing it sounds like I will get the best
> performance from moving the TempDB and the Logs files to different drives
> but which configuration would be best:
> F: TempDB DB and Logs
> G: Our main DB Log Files
> or
> F: TempDB Logs
> G: Our main DB Log Files
> or
> Something else.
> Please suggest my best route.
> Thanks!
>
>
|||Changes worked great! Thanks for the recomendations.
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:%234W8TpKhIHA.6032@.TK2MSFTNGP03.phx.gbl...
> Initially, try both data and log for tempdb. If that is satisfactory, you
> can leave it. If you still have perf issues, then move the log to another
> drive.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "Bishop" <nospam@.nospam.com> wrote in message
> news:OJ8syj7gIHA.5752@.TK2MSFTNGP03.phx.gbl...
> Hi Tom, thanks for the advice, just to clarify are you suggesting moving
> both TempDB Data and Log to G to start or just the Data?
> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
> news:Ogjz5b7gIHA.5208@.TK2MSFTNGP04.phx.gbl...
>
|||Great news. Thanx for the follow-up. :-)
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"Bishop" <nospam@.nospam.com> wrote in message
news:uDeCmGTiIHA.1164@.TK2MSFTNGP02.phx.gbl...
Changes worked great! Thanks for the recomendations.
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:%234W8TpKhIHA.6032@.TK2MSFTNGP03.phx.gbl...
> Initially, try both data and log for tempdb. If that is satisfactory, you
> can leave it. If you still have perf issues, then move the log to another
> drive.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "Bishop" <nospam@.nospam.com> wrote in message
> news:OJ8syj7gIHA.5752@.TK2MSFTNGP03.phx.gbl...
> Hi Tom, thanks for the advice, just to clarify are you suggesting moving
> both TempDB Data and Log to G to start or just the Data?
> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
> news:Ogjz5b7gIHA.5208@.TK2MSFTNGP04.phx.gbl...
>
Move Temp DB and Logs to get more speed?
We are running a server with IIS and SQL 2K using the following
configuration:
C: OS/Inetpub
D: SQL 2K DB/Logs
E: IIS Logs
F: Not Used
G: Not Used
We have a single SQL 2K DB that all the websites use.
I'm currently constrained to a single server and the drive configuration. I
would like to optimize better by using the new F: and G: drives.
Additionally the C: and D: have no problem keeping up so I could move IIS
logs to the C: drive if needed.
Based on reading I've been doing it sounds like I will get the best
performance from moving the TempDB and the Logs files to different drives
but which configuration would be best:
F: TempDB DB and Logs
G: Our main DB Log Files
or
F: TempDB Logs
G: Our main DB Log Files
or
Something else.
Please suggest my best route.
Thanks!It's a best practice to have the data and logs on separate partitions. This
is both for safety (High Availability) as well as performance. Also, try to
keep tempdb separate from your app DB's. Thus, you could go with:
D: app data
F: app log
G: tempdb
Try that first. You can also move the tempdb log to F: and see if that
improves or degrades performance. Logs should not be placed on RAID5
partitions.
HTH
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"Bishop" <nospam@.nospam.com> wrote in message
news:u20v0S7gIHA.4692@.TK2MSFTNGP05.phx.gbl...
We are running a server with IIS and SQL 2K using the following
configuration:
C: OS/Inetpub
D: SQL 2K DB/Logs
E: IIS Logs
F: Not Used
G: Not Used
We have a single SQL 2K DB that all the websites use.
I'm currently constrained to a single server and the drive configuration. I
would like to optimize better by using the new F: and G: drives.
Additionally the C: and D: have no problem keeping up so I could move IIS
logs to the C: drive if needed.
Based on reading I've been doing it sounds like I will get the best
performance from moving the TempDB and the Logs files to different drives
but which configuration would be best:
F: TempDB DB and Logs
G: Our main DB Log Files
or
F: TempDB Logs
G: Our main DB Log Files
or
Something else.
Please suggest my best route.
Thanks!|||Hi Tom, thanks for the advice, just to clarify are you suggesting moving
both TempDB Data and Log to G to start or just the Data?
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:Ogjz5b7gIHA.5208@.TK2MSFTNGP04.phx.gbl...
> It's a best practice to have the data and logs on separate partitions.
> This
> is both for safety (High Availability) as well as performance. Also, try
> to
> keep tempdb separate from your app DB's. Thus, you could go with:
> D: app data
> F: app log
> G: tempdb
> Try that first. You can also move the tempdb log to F: and see if that
> improves or degrades performance. Logs should not be placed on RAID5
> partitions.
> HTH
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "Bishop" <nospam@.nospam.com> wrote in message
> news:u20v0S7gIHA.4692@.TK2MSFTNGP05.phx.gbl...
> We are running a server with IIS and SQL 2K using the following
> configuration:
> C: OS/Inetpub
> D: SQL 2K DB/Logs
> E: IIS Logs
> F: Not Used
> G: Not Used
> We have a single SQL 2K DB that all the websites use.
> I'm currently constrained to a single server and the drive configuration.
> I
> would like to optimize better by using the new F: and G: drives.
> Additionally the C: and D: have no problem keeping up so I could move IIS
> logs to the C: drive if needed.
> Based on reading I've been doing it sounds like I will get the best
> performance from moving the TempDB and the Logs files to different drives
> but which configuration would be best:
> F: TempDB DB and Logs
> G: Our main DB Log Files
> or
> F: TempDB Logs
> G: Our main DB Log Files
> or
> Something else.
> Please suggest my best route.
> Thanks!
>
>|||Initially, try both data and log for tempdb. If that is satisfactory, you
can leave it. If you still have perf issues, then move the log to another
drive.
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"Bishop" <nospam@.nospam.com> wrote in message
news:OJ8syj7gIHA.5752@.TK2MSFTNGP03.phx.gbl...
Hi Tom, thanks for the advice, just to clarify are you suggesting moving
both TempDB Data and Log to G to start or just the Data?
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:Ogjz5b7gIHA.5208@.TK2MSFTNGP04.phx.gbl...
> It's a best practice to have the data and logs on separate partitions.
> This
> is both for safety (High Availability) as well as performance. Also, try
> to
> keep tempdb separate from your app DB's. Thus, you could go with:
> D: app data
> F: app log
> G: tempdb
> Try that first. You can also move the tempdb log to F: and see if that
> improves or degrades performance. Logs should not be placed on RAID5
> partitions.
> HTH
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "Bishop" <nospam@.nospam.com> wrote in message
> news:u20v0S7gIHA.4692@.TK2MSFTNGP05.phx.gbl...
> We are running a server with IIS and SQL 2K using the following
> configuration:
> C: OS/Inetpub
> D: SQL 2K DB/Logs
> E: IIS Logs
> F: Not Used
> G: Not Used
> We have a single SQL 2K DB that all the websites use.
> I'm currently constrained to a single server and the drive configuration.
> I
> would like to optimize better by using the new F: and G: drives.
> Additionally the C: and D: have no problem keeping up so I could move IIS
> logs to the C: drive if needed.
> Based on reading I've been doing it sounds like I will get the best
> performance from moving the TempDB and the Logs files to different drives
> but which configuration would be best:
> F: TempDB DB and Logs
> G: Our main DB Log Files
> or
> F: TempDB Logs
> G: Our main DB Log Files
> or
> Something else.
> Please suggest my best route.
> Thanks!
>
>|||Changes worked great! Thanks for the recomendations.
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:%234W8TpKhIHA.6032@.TK2MSFTNGP03.phx.gbl...
> Initially, try both data and log for tempdb. If that is satisfactory, you
> can leave it. If you still have perf issues, then move the log to another
> drive.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "Bishop" <nospam@.nospam.com> wrote in message
> news:OJ8syj7gIHA.5752@.TK2MSFTNGP03.phx.gbl...
> Hi Tom, thanks for the advice, just to clarify are you suggesting moving
> both TempDB Data and Log to G to start or just the Data?
> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
> news:Ogjz5b7gIHA.5208@.TK2MSFTNGP04.phx.gbl...
>> It's a best practice to have the data and logs on separate partitions.
>> This
>> is both for safety (High Availability) as well as performance. Also, try
>> to
>> keep tempdb separate from your app DB's. Thus, you could go with:
>> D: app data
>> F: app log
>> G: tempdb
>> Try that first. You can also move the tempdb log to F: and see if that
>> improves or degrades performance. Logs should not be placed on RAID5
>> partitions.
>> HTH
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "Bishop" <nospam@.nospam.com> wrote in message
>> news:u20v0S7gIHA.4692@.TK2MSFTNGP05.phx.gbl...
>> We are running a server with IIS and SQL 2K using the following
>> configuration:
>> C: OS/Inetpub
>> D: SQL 2K DB/Logs
>> E: IIS Logs
>> F: Not Used
>> G: Not Used
>> We have a single SQL 2K DB that all the websites use.
>> I'm currently constrained to a single server and the drive configuration.
>> I
>> would like to optimize better by using the new F: and G: drives.
>> Additionally the C: and D: have no problem keeping up so I could move IIS
>> logs to the C: drive if needed.
>> Based on reading I've been doing it sounds like I will get the best
>> performance from moving the TempDB and the Logs files to different drives
>> but which configuration would be best:
>> F: TempDB DB and Logs
>> G: Our main DB Log Files
>> or
>> F: TempDB Logs
>> G: Our main DB Log Files
>> or
>> Something else.
>> Please suggest my best route.
>> Thanks!
>>
>|||Great news. Thanx for the follow-up. :-)
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"Bishop" <nospam@.nospam.com> wrote in message
news:uDeCmGTiIHA.1164@.TK2MSFTNGP02.phx.gbl...
Changes worked great! Thanks for the recomendations.
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:%234W8TpKhIHA.6032@.TK2MSFTNGP03.phx.gbl...
> Initially, try both data and log for tempdb. If that is satisfactory, you
> can leave it. If you still have perf issues, then move the log to another
> drive.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "Bishop" <nospam@.nospam.com> wrote in message
> news:OJ8syj7gIHA.5752@.TK2MSFTNGP03.phx.gbl...
> Hi Tom, thanks for the advice, just to clarify are you suggesting moving
> both TempDB Data and Log to G to start or just the Data?
> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
> news:Ogjz5b7gIHA.5208@.TK2MSFTNGP04.phx.gbl...
>> It's a best practice to have the data and logs on separate partitions.
>> This
>> is both for safety (High Availability) as well as performance. Also, try
>> to
>> keep tempdb separate from your app DB's. Thus, you could go with:
>> D: app data
>> F: app log
>> G: tempdb
>> Try that first. You can also move the tempdb log to F: and see if that
>> improves or degrades performance. Logs should not be placed on RAID5
>> partitions.
>> HTH
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "Bishop" <nospam@.nospam.com> wrote in message
>> news:u20v0S7gIHA.4692@.TK2MSFTNGP05.phx.gbl...
>> We are running a server with IIS and SQL 2K using the following
>> configuration:
>> C: OS/Inetpub
>> D: SQL 2K DB/Logs
>> E: IIS Logs
>> F: Not Used
>> G: Not Used
>> We have a single SQL 2K DB that all the websites use.
>> I'm currently constrained to a single server and the drive configuration.
>> I
>> would like to optimize better by using the new F: and G: drives.
>> Additionally the C: and D: have no problem keeping up so I could move IIS
>> logs to the C: drive if needed.
>> Based on reading I've been doing it sounds like I will get the best
>> performance from moving the TempDB and the Logs files to different drives
>> but which configuration would be best:
>> F: TempDB DB and Logs
>> G: Our main DB Log Files
>> or
>> F: TempDB Logs
>> G: Our main DB Log Files
>> or
>> Something else.
>> Please suggest my best route.
>> Thanks!
>>
>
configuration:
C: OS/Inetpub
D: SQL 2K DB/Logs
E: IIS Logs
F: Not Used
G: Not Used
We have a single SQL 2K DB that all the websites use.
I'm currently constrained to a single server and the drive configuration. I
would like to optimize better by using the new F: and G: drives.
Additionally the C: and D: have no problem keeping up so I could move IIS
logs to the C: drive if needed.
Based on reading I've been doing it sounds like I will get the best
performance from moving the TempDB and the Logs files to different drives
but which configuration would be best:
F: TempDB DB and Logs
G: Our main DB Log Files
or
F: TempDB Logs
G: Our main DB Log Files
or
Something else.
Please suggest my best route.
Thanks!It's a best practice to have the data and logs on separate partitions. This
is both for safety (High Availability) as well as performance. Also, try to
keep tempdb separate from your app DB's. Thus, you could go with:
D: app data
F: app log
G: tempdb
Try that first. You can also move the tempdb log to F: and see if that
improves or degrades performance. Logs should not be placed on RAID5
partitions.
HTH
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"Bishop" <nospam@.nospam.com> wrote in message
news:u20v0S7gIHA.4692@.TK2MSFTNGP05.phx.gbl...
We are running a server with IIS and SQL 2K using the following
configuration:
C: OS/Inetpub
D: SQL 2K DB/Logs
E: IIS Logs
F: Not Used
G: Not Used
We have a single SQL 2K DB that all the websites use.
I'm currently constrained to a single server and the drive configuration. I
would like to optimize better by using the new F: and G: drives.
Additionally the C: and D: have no problem keeping up so I could move IIS
logs to the C: drive if needed.
Based on reading I've been doing it sounds like I will get the best
performance from moving the TempDB and the Logs files to different drives
but which configuration would be best:
F: TempDB DB and Logs
G: Our main DB Log Files
or
F: TempDB Logs
G: Our main DB Log Files
or
Something else.
Please suggest my best route.
Thanks!|||Hi Tom, thanks for the advice, just to clarify are you suggesting moving
both TempDB Data and Log to G to start or just the Data?
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:Ogjz5b7gIHA.5208@.TK2MSFTNGP04.phx.gbl...
> It's a best practice to have the data and logs on separate partitions.
> This
> is both for safety (High Availability) as well as performance. Also, try
> to
> keep tempdb separate from your app DB's. Thus, you could go with:
> D: app data
> F: app log
> G: tempdb
> Try that first. You can also move the tempdb log to F: and see if that
> improves or degrades performance. Logs should not be placed on RAID5
> partitions.
> HTH
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "Bishop" <nospam@.nospam.com> wrote in message
> news:u20v0S7gIHA.4692@.TK2MSFTNGP05.phx.gbl...
> We are running a server with IIS and SQL 2K using the following
> configuration:
> C: OS/Inetpub
> D: SQL 2K DB/Logs
> E: IIS Logs
> F: Not Used
> G: Not Used
> We have a single SQL 2K DB that all the websites use.
> I'm currently constrained to a single server and the drive configuration.
> I
> would like to optimize better by using the new F: and G: drives.
> Additionally the C: and D: have no problem keeping up so I could move IIS
> logs to the C: drive if needed.
> Based on reading I've been doing it sounds like I will get the best
> performance from moving the TempDB and the Logs files to different drives
> but which configuration would be best:
> F: TempDB DB and Logs
> G: Our main DB Log Files
> or
> F: TempDB Logs
> G: Our main DB Log Files
> or
> Something else.
> Please suggest my best route.
> Thanks!
>
>|||Initially, try both data and log for tempdb. If that is satisfactory, you
can leave it. If you still have perf issues, then move the log to another
drive.
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"Bishop" <nospam@.nospam.com> wrote in message
news:OJ8syj7gIHA.5752@.TK2MSFTNGP03.phx.gbl...
Hi Tom, thanks for the advice, just to clarify are you suggesting moving
both TempDB Data and Log to G to start or just the Data?
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:Ogjz5b7gIHA.5208@.TK2MSFTNGP04.phx.gbl...
> It's a best practice to have the data and logs on separate partitions.
> This
> is both for safety (High Availability) as well as performance. Also, try
> to
> keep tempdb separate from your app DB's. Thus, you could go with:
> D: app data
> F: app log
> G: tempdb
> Try that first. You can also move the tempdb log to F: and see if that
> improves or degrades performance. Logs should not be placed on RAID5
> partitions.
> HTH
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "Bishop" <nospam@.nospam.com> wrote in message
> news:u20v0S7gIHA.4692@.TK2MSFTNGP05.phx.gbl...
> We are running a server with IIS and SQL 2K using the following
> configuration:
> C: OS/Inetpub
> D: SQL 2K DB/Logs
> E: IIS Logs
> F: Not Used
> G: Not Used
> We have a single SQL 2K DB that all the websites use.
> I'm currently constrained to a single server and the drive configuration.
> I
> would like to optimize better by using the new F: and G: drives.
> Additionally the C: and D: have no problem keeping up so I could move IIS
> logs to the C: drive if needed.
> Based on reading I've been doing it sounds like I will get the best
> performance from moving the TempDB and the Logs files to different drives
> but which configuration would be best:
> F: TempDB DB and Logs
> G: Our main DB Log Files
> or
> F: TempDB Logs
> G: Our main DB Log Files
> or
> Something else.
> Please suggest my best route.
> Thanks!
>
>|||Changes worked great! Thanks for the recomendations.
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:%234W8TpKhIHA.6032@.TK2MSFTNGP03.phx.gbl...
> Initially, try both data and log for tempdb. If that is satisfactory, you
> can leave it. If you still have perf issues, then move the log to another
> drive.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "Bishop" <nospam@.nospam.com> wrote in message
> news:OJ8syj7gIHA.5752@.TK2MSFTNGP03.phx.gbl...
> Hi Tom, thanks for the advice, just to clarify are you suggesting moving
> both TempDB Data and Log to G to start or just the Data?
> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
> news:Ogjz5b7gIHA.5208@.TK2MSFTNGP04.phx.gbl...
>> It's a best practice to have the data and logs on separate partitions.
>> This
>> is both for safety (High Availability) as well as performance. Also, try
>> to
>> keep tempdb separate from your app DB's. Thus, you could go with:
>> D: app data
>> F: app log
>> G: tempdb
>> Try that first. You can also move the tempdb log to F: and see if that
>> improves or degrades performance. Logs should not be placed on RAID5
>> partitions.
>> HTH
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "Bishop" <nospam@.nospam.com> wrote in message
>> news:u20v0S7gIHA.4692@.TK2MSFTNGP05.phx.gbl...
>> We are running a server with IIS and SQL 2K using the following
>> configuration:
>> C: OS/Inetpub
>> D: SQL 2K DB/Logs
>> E: IIS Logs
>> F: Not Used
>> G: Not Used
>> We have a single SQL 2K DB that all the websites use.
>> I'm currently constrained to a single server and the drive configuration.
>> I
>> would like to optimize better by using the new F: and G: drives.
>> Additionally the C: and D: have no problem keeping up so I could move IIS
>> logs to the C: drive if needed.
>> Based on reading I've been doing it sounds like I will get the best
>> performance from moving the TempDB and the Logs files to different drives
>> but which configuration would be best:
>> F: TempDB DB and Logs
>> G: Our main DB Log Files
>> or
>> F: TempDB Logs
>> G: Our main DB Log Files
>> or
>> Something else.
>> Please suggest my best route.
>> Thanks!
>>
>|||Great news. Thanx for the follow-up. :-)
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"Bishop" <nospam@.nospam.com> wrote in message
news:uDeCmGTiIHA.1164@.TK2MSFTNGP02.phx.gbl...
Changes worked great! Thanks for the recomendations.
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:%234W8TpKhIHA.6032@.TK2MSFTNGP03.phx.gbl...
> Initially, try both data and log for tempdb. If that is satisfactory, you
> can leave it. If you still have perf issues, then move the log to another
> drive.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "Bishop" <nospam@.nospam.com> wrote in message
> news:OJ8syj7gIHA.5752@.TK2MSFTNGP03.phx.gbl...
> Hi Tom, thanks for the advice, just to clarify are you suggesting moving
> both TempDB Data and Log to G to start or just the Data?
> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
> news:Ogjz5b7gIHA.5208@.TK2MSFTNGP04.phx.gbl...
>> It's a best practice to have the data and logs on separate partitions.
>> This
>> is both for safety (High Availability) as well as performance. Also, try
>> to
>> keep tempdb separate from your app DB's. Thus, you could go with:
>> D: app data
>> F: app log
>> G: tempdb
>> Try that first. You can also move the tempdb log to F: and see if that
>> improves or degrades performance. Logs should not be placed on RAID5
>> partitions.
>> HTH
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "Bishop" <nospam@.nospam.com> wrote in message
>> news:u20v0S7gIHA.4692@.TK2MSFTNGP05.phx.gbl...
>> We are running a server with IIS and SQL 2K using the following
>> configuration:
>> C: OS/Inetpub
>> D: SQL 2K DB/Logs
>> E: IIS Logs
>> F: Not Used
>> G: Not Used
>> We have a single SQL 2K DB that all the websites use.
>> I'm currently constrained to a single server and the drive configuration.
>> I
>> would like to optimize better by using the new F: and G: drives.
>> Additionally the C: and D: have no problem keeping up so I could move IIS
>> logs to the C: drive if needed.
>> Based on reading I've been doing it sounds like I will get the best
>> performance from moving the TempDB and the Logs files to different drives
>> but which configuration would be best:
>> F: TempDB DB and Logs
>> G: Our main DB Log Files
>> or
>> F: TempDB Logs
>> G: Our main DB Log Files
>> or
>> Something else.
>> Please suggest my best route.
>> Thanks!
>>
>
Friday, March 9, 2012
Move Logs to another drive
Does anyone know how to move the SQL logs to another drive. I want to
seperate these from the database for redundancy and performance
I get an error stating the log cannot be moved after the database has been
create.
SQL 2000 STD
Thanks in advance for your helpSee sp_detach/ sp_attach in BOL.
"Bob Smith" <BobSmith@.discussions.microsoft.com> wrote in message
news:D14C7D37-BCF5-4D79-ACCE-95C1F75C4783@.microsoft.com...
> Does anyone know how to move the SQL logs to another drive. I want to
> seperate these from the database for redundancy and performance
> I get an error stating the log cannot be moved after the database has been
> create.
> SQL 2000 STD
> Thanks in advance for your help|||"Bob Smith" <BobSmith@.discussions.microsoft.com> wrote in message
news:D14C7D37-BCF5-4D79-ACCE-95C1F75C4783@.microsoft.com...
> Does anyone know how to move the SQL logs to another drive. I want to
> seperate these from the database for redundancy and performance
> I get an error stating the log cannot be moved after the database has been
> create.
> SQL 2000 STD
> Thanks in advance for your help
sp_attach_db and sp_detach_db can help you here.
Alternately, you could issue a RESTORE DATABASE command specify the new
location using the MOVE TO option.
Rick Sawtell
MCT, MCSD, MCDBA
seperate these from the database for redundancy and performance
I get an error stating the log cannot be moved after the database has been
create.
SQL 2000 STD
Thanks in advance for your helpSee sp_detach/ sp_attach in BOL.
"Bob Smith" <BobSmith@.discussions.microsoft.com> wrote in message
news:D14C7D37-BCF5-4D79-ACCE-95C1F75C4783@.microsoft.com...
> Does anyone know how to move the SQL logs to another drive. I want to
> seperate these from the database for redundancy and performance
> I get an error stating the log cannot be moved after the database has been
> create.
> SQL 2000 STD
> Thanks in advance for your help|||"Bob Smith" <BobSmith@.discussions.microsoft.com> wrote in message
news:D14C7D37-BCF5-4D79-ACCE-95C1F75C4783@.microsoft.com...
> Does anyone know how to move the SQL logs to another drive. I want to
> seperate these from the database for redundancy and performance
> I get an error stating the log cannot be moved after the database has been
> create.
> SQL 2000 STD
> Thanks in advance for your help
sp_attach_db and sp_detach_db can help you here.
Alternately, you could issue a RESTORE DATABASE command specify the new
location using the MOVE TO option.
Rick Sawtell
MCT, MCSD, MCDBA
Move Logs to another drive
Does anyone know how to move the SQL logs to another drive. I want to
seperate these from the database for redundancy and performance
I get an error stating the log cannot be moved after the database has been
create.
SQL 2000 STD
Thanks in advance for your help
See sp_detach/ sp_attach in BOL.
"Bob Smith" <BobSmith@.discussions.microsoft.com> wrote in message
news:D14C7D37-BCF5-4D79-ACCE-95C1F75C4783@.microsoft.com...
> Does anyone know how to move the SQL logs to another drive. I want to
> seperate these from the database for redundancy and performance
> I get an error stating the log cannot be moved after the database has been
> create.
> SQL 2000 STD
> Thanks in advance for your help
|||"Bob Smith" <BobSmith@.discussions.microsoft.com> wrote in message
news:D14C7D37-BCF5-4D79-ACCE-95C1F75C4783@.microsoft.com...
> Does anyone know how to move the SQL logs to another drive. I want to
> seperate these from the database for redundancy and performance
> I get an error stating the log cannot be moved after the database has been
> create.
> SQL 2000 STD
> Thanks in advance for your help
sp_attach_db and sp_detach_db can help you here.
Alternately, you could issue a RESTORE DATABASE command specify the new
location using the MOVE TO option.
Rick Sawtell
MCT, MCSD, MCDBA
seperate these from the database for redundancy and performance
I get an error stating the log cannot be moved after the database has been
create.
SQL 2000 STD
Thanks in advance for your help
See sp_detach/ sp_attach in BOL.
"Bob Smith" <BobSmith@.discussions.microsoft.com> wrote in message
news:D14C7D37-BCF5-4D79-ACCE-95C1F75C4783@.microsoft.com...
> Does anyone know how to move the SQL logs to another drive. I want to
> seperate these from the database for redundancy and performance
> I get an error stating the log cannot be moved after the database has been
> create.
> SQL 2000 STD
> Thanks in advance for your help
|||"Bob Smith" <BobSmith@.discussions.microsoft.com> wrote in message
news:D14C7D37-BCF5-4D79-ACCE-95C1F75C4783@.microsoft.com...
> Does anyone know how to move the SQL logs to another drive. I want to
> seperate these from the database for redundancy and performance
> I get an error stating the log cannot be moved after the database has been
> create.
> SQL 2000 STD
> Thanks in advance for your help
sp_attach_db and sp_detach_db can help you here.
Alternately, you could issue a RESTORE DATABASE command specify the new
location using the MOVE TO option.
Rick Sawtell
MCT, MCSD, MCDBA
Move Logs to another drive
Does anyone know how to move the SQL logs to another drive. I want to
seperate these from the database for redundancy and performance
I get an error stating the log cannot be moved after the database has been
create.
SQL 2000 STD
Thanks in advance for your helpSee sp_detach/ sp_attach in BOL.
"Bob Smith" <BobSmith@.discussions.microsoft.com> wrote in message
news:D14C7D37-BCF5-4D79-ACCE-95C1F75C4783@.microsoft.com...
> Does anyone know how to move the SQL logs to another drive. I want to
> seperate these from the database for redundancy and performance
> I get an error stating the log cannot be moved after the database has been
> create.
> SQL 2000 STD
> Thanks in advance for your help|||"Bob Smith" <BobSmith@.discussions.microsoft.com> wrote in message
news:D14C7D37-BCF5-4D79-ACCE-95C1F75C4783@.microsoft.com...
> Does anyone know how to move the SQL logs to another drive. I want to
> seperate these from the database for redundancy and performance
> I get an error stating the log cannot be moved after the database has been
> create.
> SQL 2000 STD
> Thanks in advance for your help
sp_attach_db and sp_detach_db can help you here.
Alternately, you could issue a RESTORE DATABASE command specify the new
location using the MOVE TO option.
Rick Sawtell
MCT, MCSD, MCDBA
seperate these from the database for redundancy and performance
I get an error stating the log cannot be moved after the database has been
create.
SQL 2000 STD
Thanks in advance for your helpSee sp_detach/ sp_attach in BOL.
"Bob Smith" <BobSmith@.discussions.microsoft.com> wrote in message
news:D14C7D37-BCF5-4D79-ACCE-95C1F75C4783@.microsoft.com...
> Does anyone know how to move the SQL logs to another drive. I want to
> seperate these from the database for redundancy and performance
> I get an error stating the log cannot be moved after the database has been
> create.
> SQL 2000 STD
> Thanks in advance for your help|||"Bob Smith" <BobSmith@.discussions.microsoft.com> wrote in message
news:D14C7D37-BCF5-4D79-ACCE-95C1F75C4783@.microsoft.com...
> Does anyone know how to move the SQL logs to another drive. I want to
> seperate these from the database for redundancy and performance
> I get an error stating the log cannot be moved after the database has been
> create.
> SQL 2000 STD
> Thanks in advance for your help
sp_attach_db and sp_detach_db can help you here.
Alternately, you could issue a RESTORE DATABASE command specify the new
location using the MOVE TO option.
Rick Sawtell
MCT, MCSD, MCDBA
Move Log Files From C:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\LOG To E:\MSSQL Logs
How do I move the default log files placed in: C:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\LOG to a different location? I want to place them in a partition I have setup which stores log files? Reason being is that this log directory is getting quite large, 600MB and I want to conserve space on my C:\ partition.
Thanks.
You can move the files using sp_detach_db and sp_attach_db. You can find the steps explained in the following article:
How to move SQL Server databases to a new location by using Detach and Attach functions in SQL Server
http://support.microsoft.com/kb/224071
-Sue
|||Sue:
Acutally I dont want to move any database files, what I want to move is simply the log files, just errors, activity and such. The files reside in the /log directory not the /data directory.
Thanks for the help.
|||For the SQL error log, open up SQL Server Configuration Manager. Select the SQL Services node, double click on SQL Server in the right pane and go to the advanced tab. View the startup parameters. The path following -e is for the error log. See the books online topic: Using the SQL Server Service Startup Options.
You can use Configuration Manager to change the path for SQL Agent as well. Select the service node, double click on SQL Server agent and go to the advanced tab. Change the path for the dump directory.
In terms of the default trace, that will default to your installation directory. You can create your own trace if you want another location.
-Sue
|||Thanks Sue that did the trick.
Changed dump directory to: E:\MSSQL and startup parameters e to E:\MSSQL\ERRORLOG and restarted the service.
Monday, February 20, 2012
Move Database and Relocate Transaction Logs
Hello,
We have just built a Windows 2000 Advance Server with SQL Server 2000
Enterprise Edition. We would like to move some databases off of an old SQL
2000 Server onto this new server.
Questions:
What is the proper procedure for moving these databases over?
Once the databases are transferred, how can we relocate all of the
transaction logs (master, model, tempdb and databases we have created) to
another drive?
Thanks,
JBaileyCheckout the Copy Database Wizard, you can specify where
the files get copied to. It doesn't copy system
databases, but should grab most relevant material from
them.
>--Original Message--
>Hello,
>We have just built a Windows 2000 Advance Server with SQL
Server 2000
>Enterprise Edition. We would like to move some databases
off of an old SQL
>2000 Server onto this new server.
>Questions:
>What is the proper procedure for moving these databases
over?
>Once the databases are transferred, how can we relocate
all of the
>transaction logs (master, model, tempdb and databases we
have created) to
>another drive?
>Thanks,
>JBailey
>
>.
>|||Best place to start is reading 224071. Also, CDW as recommended by .. is an option.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as ugroup=microsoft.public.sqlserver
"JBailey" <abc@.123.com> wrote in message news:ucrE451kDHA.2424@.TK2MSFTNGP10.phx.gbl...
> Hello,
> We have just built a Windows 2000 Advance Server with SQL Server 2000
> Enterprise Edition. We would like to move some databases off of an old SQL
> 2000 Server onto this new server.
> Questions:
> What is the proper procedure for moving these databases over?
> Once the databases are transferred, how can we relocate all of the
> transaction logs (master, model, tempdb and databases we have created) to
> another drive?
> Thanks,
> JBailey
>|||Tibor,
224071 ? I cant seem to find that, have a link?
Thanks,
"Tibor Karaszi" <tibor.please_reply_to_public_forum.karaszi@.cornerstone.se>
wrote in message news:ehGA9E7kDHA.2012@.TK2MSFTNGP12.phx.gbl...
> Best place to start is reading 224071. Also, CDW as recommended by .. is
an option.
> --
> Tibor Karaszi, SQL Server MVP
> Archive at: http://groups.google.com/groups?oi=djq&as
ugroup=microsoft.public.sqlserver
>
> "JBailey" <abc@.123.com> wrote in message
news:ucrE451kDHA.2424@.TK2MSFTNGP10.phx.gbl...
> > Hello,
> >
> > We have just built a Windows 2000 Advance Server with SQL Server 2000
> > Enterprise Edition. We would like to move some databases off of an old
SQL
> > 2000 Server onto this new server.
> >
> > Questions:
> >
> > What is the proper procedure for moving these databases over?
> > Once the databases are transferred, how can we relocate all of the
> > transaction logs (master, model, tempdb and databases we have created)
to
> > another drive?
> >
> > Thanks,
> >
> > JBailey
> >
> >
>|||Found 224071.
Questions:
Is it necessary to move the master, model, and tempdb over? Or can I just
move the databases we created? Is there dependencies user created databases
have on the default SQL databases that I should be aware of?
Thanks,
JBailey
"Tibor Karaszi" <tibor.please_reply_to_public_forum.karaszi@.cornerstone.se>
wrote in message news:ehGA9E7kDHA.2012@.TK2MSFTNGP12.phx.gbl...
> Best place to start is reading 224071. Also, CDW as recommended by .. is
an option.
> --
> Tibor Karaszi, SQL Server MVP
> Archive at: http://groups.google.com/groups?oi=djq&as
ugroup=microsoft.public.sqlserver
>
> "JBailey" <abc@.123.com> wrote in message
news:ucrE451kDHA.2424@.TK2MSFTNGP10.phx.gbl...
> > Hello,
> >
> > We have just built a Windows 2000 Advance Server with SQL Server 2000
> > Enterprise Edition. We would like to move some databases off of an old
SQL
> > 2000 Server onto this new server.
> >
> > Questions:
> >
> > What is the proper procedure for moving these databases over?
> > Once the databases are transferred, how can we relocate all of the
> > transaction logs (master, model, tempdb and databases we have created)
to
> > another drive?
> >
> > Thanks,
> >
> > JBailey
> >
> >
>|||You can to consider what is stored in the system databases. In master, you have logins, linked
servers, sysmessages, sp_configure. In msdb, you have jobs, operators, alerts.
Only you can say whether above is a too huge job to do manually compared to try to get backup etc
over to the new server.
As for logins (which generally is the main issue), read in books online about sp_change_users_login
and you might want to use the GUI tool at www.dbmaint.com (free utilities).
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as ugroup=microsoft.public.sqlserver
"JBailey" <abc@.123.com> wrote in message news:OXwiR3%23kDHA.2364@.TK2MSFTNGP11.phx.gbl...
> Found 224071.
> Questions:
> Is it necessary to move the master, model, and tempdb over? Or can I just
> move the databases we created? Is there dependencies user created databases
> have on the default SQL databases that I should be aware of?
> Thanks,
> JBailey
>
> "Tibor Karaszi" <tibor.please_reply_to_public_forum.karaszi@.cornerstone.se>
> wrote in message news:ehGA9E7kDHA.2012@.TK2MSFTNGP12.phx.gbl...
> > Best place to start is reading 224071. Also, CDW as recommended by .. is
> an option.
> >
> > --
> > Tibor Karaszi, SQL Server MVP
> > Archive at: http://groups.google.com/groups?oi=djq&as
> ugroup=microsoft.public.sqlserver
> >
> >
> > "JBailey" <abc@.123.com> wrote in message
> news:ucrE451kDHA.2424@.TK2MSFTNGP10.phx.gbl...
> > > Hello,
> > >
> > > We have just built a Windows 2000 Advance Server with SQL Server 2000
> > > Enterprise Edition. We would like to move some databases off of an old
> SQL
> > > 2000 Server onto this new server.
> > >
> > > Questions:
> > >
> > > What is the proper procedure for moving these databases over?
> > > Once the databases are transferred, how can we relocate all of the
> > > transaction logs (master, model, tempdb and databases we have created)
> to
> > > another drive?
> > >
> > > Thanks,
> > >
> > > JBailey
> > >
> > >
> >
> >
>
We have just built a Windows 2000 Advance Server with SQL Server 2000
Enterprise Edition. We would like to move some databases off of an old SQL
2000 Server onto this new server.
Questions:
What is the proper procedure for moving these databases over?
Once the databases are transferred, how can we relocate all of the
transaction logs (master, model, tempdb and databases we have created) to
another drive?
Thanks,
JBaileyCheckout the Copy Database Wizard, you can specify where
the files get copied to. It doesn't copy system
databases, but should grab most relevant material from
them.
>--Original Message--
>Hello,
>We have just built a Windows 2000 Advance Server with SQL
Server 2000
>Enterprise Edition. We would like to move some databases
off of an old SQL
>2000 Server onto this new server.
>Questions:
>What is the proper procedure for moving these databases
over?
>Once the databases are transferred, how can we relocate
all of the
>transaction logs (master, model, tempdb and databases we
have created) to
>another drive?
>Thanks,
>JBailey
>
>.
>|||Best place to start is reading 224071. Also, CDW as recommended by .. is an option.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as ugroup=microsoft.public.sqlserver
"JBailey" <abc@.123.com> wrote in message news:ucrE451kDHA.2424@.TK2MSFTNGP10.phx.gbl...
> Hello,
> We have just built a Windows 2000 Advance Server with SQL Server 2000
> Enterprise Edition. We would like to move some databases off of an old SQL
> 2000 Server onto this new server.
> Questions:
> What is the proper procedure for moving these databases over?
> Once the databases are transferred, how can we relocate all of the
> transaction logs (master, model, tempdb and databases we have created) to
> another drive?
> Thanks,
> JBailey
>|||Tibor,
224071 ? I cant seem to find that, have a link?
Thanks,
"Tibor Karaszi" <tibor.please_reply_to_public_forum.karaszi@.cornerstone.se>
wrote in message news:ehGA9E7kDHA.2012@.TK2MSFTNGP12.phx.gbl...
> Best place to start is reading 224071. Also, CDW as recommended by .. is
an option.
> --
> Tibor Karaszi, SQL Server MVP
> Archive at: http://groups.google.com/groups?oi=djq&as
ugroup=microsoft.public.sqlserver
>
> "JBailey" <abc@.123.com> wrote in message
news:ucrE451kDHA.2424@.TK2MSFTNGP10.phx.gbl...
> > Hello,
> >
> > We have just built a Windows 2000 Advance Server with SQL Server 2000
> > Enterprise Edition. We would like to move some databases off of an old
SQL
> > 2000 Server onto this new server.
> >
> > Questions:
> >
> > What is the proper procedure for moving these databases over?
> > Once the databases are transferred, how can we relocate all of the
> > transaction logs (master, model, tempdb and databases we have created)
to
> > another drive?
> >
> > Thanks,
> >
> > JBailey
> >
> >
>|||Found 224071.
Questions:
Is it necessary to move the master, model, and tempdb over? Or can I just
move the databases we created? Is there dependencies user created databases
have on the default SQL databases that I should be aware of?
Thanks,
JBailey
"Tibor Karaszi" <tibor.please_reply_to_public_forum.karaszi@.cornerstone.se>
wrote in message news:ehGA9E7kDHA.2012@.TK2MSFTNGP12.phx.gbl...
> Best place to start is reading 224071. Also, CDW as recommended by .. is
an option.
> --
> Tibor Karaszi, SQL Server MVP
> Archive at: http://groups.google.com/groups?oi=djq&as
ugroup=microsoft.public.sqlserver
>
> "JBailey" <abc@.123.com> wrote in message
news:ucrE451kDHA.2424@.TK2MSFTNGP10.phx.gbl...
> > Hello,
> >
> > We have just built a Windows 2000 Advance Server with SQL Server 2000
> > Enterprise Edition. We would like to move some databases off of an old
SQL
> > 2000 Server onto this new server.
> >
> > Questions:
> >
> > What is the proper procedure for moving these databases over?
> > Once the databases are transferred, how can we relocate all of the
> > transaction logs (master, model, tempdb and databases we have created)
to
> > another drive?
> >
> > Thanks,
> >
> > JBailey
> >
> >
>|||You can to consider what is stored in the system databases. In master, you have logins, linked
servers, sysmessages, sp_configure. In msdb, you have jobs, operators, alerts.
Only you can say whether above is a too huge job to do manually compared to try to get backup etc
over to the new server.
As for logins (which generally is the main issue), read in books online about sp_change_users_login
and you might want to use the GUI tool at www.dbmaint.com (free utilities).
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as ugroup=microsoft.public.sqlserver
"JBailey" <abc@.123.com> wrote in message news:OXwiR3%23kDHA.2364@.TK2MSFTNGP11.phx.gbl...
> Found 224071.
> Questions:
> Is it necessary to move the master, model, and tempdb over? Or can I just
> move the databases we created? Is there dependencies user created databases
> have on the default SQL databases that I should be aware of?
> Thanks,
> JBailey
>
> "Tibor Karaszi" <tibor.please_reply_to_public_forum.karaszi@.cornerstone.se>
> wrote in message news:ehGA9E7kDHA.2012@.TK2MSFTNGP12.phx.gbl...
> > Best place to start is reading 224071. Also, CDW as recommended by .. is
> an option.
> >
> > --
> > Tibor Karaszi, SQL Server MVP
> > Archive at: http://groups.google.com/groups?oi=djq&as
> ugroup=microsoft.public.sqlserver
> >
> >
> > "JBailey" <abc@.123.com> wrote in message
> news:ucrE451kDHA.2424@.TK2MSFTNGP10.phx.gbl...
> > > Hello,
> > >
> > > We have just built a Windows 2000 Advance Server with SQL Server 2000
> > > Enterprise Edition. We would like to move some databases off of an old
> SQL
> > > 2000 Server onto this new server.
> > >
> > > Questions:
> > >
> > > What is the proper procedure for moving these databases over?
> > > Once the databases are transferred, how can we relocate all of the
> > > transaction logs (master, model, tempdb and databases we have created)
> to
> > > another drive?
> > >
> > > Thanks,
> > >
> > > JBailey
> > >
> > >
> >
> >
>
Subscribe to:
Posts (Atom)