I saw an article about monitoring drive usage:
http://www.sqlservercentral.com/columnists/hji/monitoringdiskspaceandsendingalertswithtsql.asp
It relies on the undocumented 'master..xp_fixeddrives' extended procedure in
2000. Now, it's not documented in 2005 either, but I've been reading the
results from a technet search on 'xp_fixeddrives' and it looks like it's in
SQL Server for the long haul.
https://blogs.technet.com/mscom/archive/2007/01/18/keeping-track-of-database-capacity-monitoring-and-planning.aspx
Should I use it?Hi Jay
You could argue that if this is used for an administrative task it is not in
the scope of the critical application functionality and therefore
permissable... but on the other hand any code on a live system could be
deemed as critical!!! Bottom line the choice is up to you, if you do decide
to use it then it should be noted and documented. Any upgrades should
specifically check that this is still available and functions in the same
way. You may want to look at writing your own script such as the perl script
http://support.microsoft.com/default.aspx/kb/318762
John
"Jay" wrote:
> I saw an article about monitoring drive usage:
> http://www.sqlservercentral.com/columnists/hji/monitoringdiskspaceandsendingalertswithtsql.asp
> It relies on the undocumented 'master..xp_fixeddrives' extended procedure in
> 2000. Now, it's not documented in 2005 either, but I've been reading the
> results from a technet search on 'xp_fixeddrives' and it looks like it's in
> SQL Server for the long haul.
> https://blogs.technet.com/mscom/archive/2007/01/18/keeping-track-of-database-capacity-monitoring-and-planning.aspx
> Should I use it?
>
>
Showing posts with label drive. Show all posts
Showing posts with label drive. Show all posts
Monday, February 20, 2012
Master, Tempdb, Msdb, Model?
I am looking for an opinion here...
What do most people do about these databases, leave the data & log file on t
he same drive
-or-
Move the log files to a separate drive?
I have the info on how to move the log files, and I do place my user databas
e & logs on separate drives, but I am not sure of what a "best practice" is
for the Sql system databases.
Any opinions are appreciated!I would put the temp DB on a seperate drive as well
http://sqlservercode.blogspot.com/
"JLS" wrote:
> I am looking for an opinion here...
> What do most people do about these databases, leave the data & log file on
the same drive
> -or-
> Move the log files to a separate drive?
> I have the info on how to move the log files, and I do place my user datab
ase & logs on separate drives, but I am not sure of what a "best practice" i
s for the Sql system databases.
> Any opinions are appreciated!
>|||And also move the log file to a separate file
"JLS" wrote:
> I am looking for an opinion here...
> What do most people do about these databases, leave the data & log file on
the same drive
> -or-
> Move the log files to a separate drive?
> I have the info on how to move the log files, and I do place my user datab
ase & logs on separate drives, but I am not sure of what a "best practice" i
s for the Sql system databases.
> Any opinions are appreciated!
>|||I use to have data and log on same drive for system databases. The possible
exception is tempdb.
This can be a high-activity database, so same reasoning goes for tempdb as f
or other databases.
Also, moving database files for system databases is a bit special, so read K
B 224071.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"JLS" <jlshoop@.hotmail.com> wrote in message news:%23nzSw2PxFHA.2132@.TK2MSFT
NGP15.phx.gbl...
I am looking for an opinion here...
What do most people do about these databases, leave the data & log file on t
he same drive
-or-
Move the log files to a separate drive?
I have the info on how to move the log files, and I do place my user databas
e & logs on separate
drives, but I am not sure of what a "best practice" is for the Sql system da
tabases.
Any opinions are appreciated!|||Thanx everyone!
"JLS" <jlshoop@.hotmail.com> wrote in message news:%23nzSw2PxFHA.2132@.TK2MSFT
NGP15.phx.gbl...
I am looking for an opinion here...
What do most people do about these databases, leave the data & log file on t
he same drive
-or-
Move the log files to a separate drive?
I have the info on how to move the log files, and I do place my user databas
e & logs on separate drives, but I am not sure of what a "best practice" is
for the Sql system databases.
Any opinions are appreciated!
What do most people do about these databases, leave the data & log file on t
he same drive
-or-
Move the log files to a separate drive?
I have the info on how to move the log files, and I do place my user databas
e & logs on separate drives, but I am not sure of what a "best practice" is
for the Sql system databases.
Any opinions are appreciated!I would put the temp DB on a seperate drive as well
http://sqlservercode.blogspot.com/
"JLS" wrote:
> I am looking for an opinion here...
> What do most people do about these databases, leave the data & log file on
the same drive
> -or-
> Move the log files to a separate drive?
> I have the info on how to move the log files, and I do place my user datab
ase & logs on separate drives, but I am not sure of what a "best practice" i
s for the Sql system databases.
> Any opinions are appreciated!
>|||And also move the log file to a separate file
"JLS" wrote:
> I am looking for an opinion here...
> What do most people do about these databases, leave the data & log file on
the same drive
> -or-
> Move the log files to a separate drive?
> I have the info on how to move the log files, and I do place my user datab
ase & logs on separate drives, but I am not sure of what a "best practice" i
s for the Sql system databases.
> Any opinions are appreciated!
>|||I use to have data and log on same drive for system databases. The possible
exception is tempdb.
This can be a high-activity database, so same reasoning goes for tempdb as f
or other databases.
Also, moving database files for system databases is a bit special, so read K
B 224071.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"JLS" <jlshoop@.hotmail.com> wrote in message news:%23nzSw2PxFHA.2132@.TK2MSFT
NGP15.phx.gbl...
I am looking for an opinion here...
What do most people do about these databases, leave the data & log file on t
he same drive
-or-
Move the log files to a separate drive?
I have the info on how to move the log files, and I do place my user databas
e & logs on separate
drives, but I am not sure of what a "best practice" is for the Sql system da
tabases.
Any opinions are appreciated!|||Thanx everyone!
"JLS" <jlshoop@.hotmail.com> wrote in message news:%23nzSw2PxFHA.2132@.TK2MSFT
NGP15.phx.gbl...
I am looking for an opinion here...
What do most people do about these databases, leave the data & log file on t
he same drive
-or-
Move the log files to a separate drive?
I have the info on how to move the log files, and I do place my user databas
e & logs on separate drives, but I am not sure of what a "best practice" is
for the Sql system databases.
Any opinions are appreciated!
Subscribe to:
Comments (Atom)