|
|
|
Old Hand
      
Group: General Forum Members
Last Login: Today @ 11:32 AM
Points: 309,
Visits: 720
|
|
The mess I've inherited:
WS2K3 / SQL Server 2K5 installed on c: A few pretty big databases 3 x 200GB, data on d: logs on e:
Somehow poorly written queries seem to consume gigs of space on c: How can that be? Data is on D & E. A reboot reclaims the space.
Sorry if this is boring stuff. I'm a programmer. I write code. I know MSSQL well enough to write some pretty dang good queries. But this DBA stuff has me baffled. Love to tackle it if I can get some time away from the burning fires and the smell of flesh.
Any insight on my dilema, and maybe a book recommedation for me? Something along the lines of "so you wanna be dba", or "so now you own the data".
Thanks in advance for any help you might have to offer.
.
|
|
|
|
|
SSCrazy
      
Group: General Forum Members
Last Login: Today @ 7:55 AM
Points: 2,639,
Visits: 4,549
|
|
I would check for the location of the system databases, specifically tempdb. It sounds like this is on the default C drive and growing with your big queries.
I would move it (Tempdb) if at all possible (and definitely move it's log to a different drive to it's data). ALTER DATABASE in Books on line describes the procedure for moving it.
Mike
|
|
|
|
|
SSC-Addicted
      
Group: General Forum Members
Last Login: Tuesday, March 19, 2013 2:45 AM
Points: 416,
Visits: 521
|
|
|
|
|
|
SSCommitted
      
Group: General Forum Members
Last Login: Thursday, May 05, 2011 1:38 AM
Points: 1,636,
Visits: 604
|
|
I would suggest to move TEMPDB on yet another separate drive. One drive for data, one for logs, one for TEMPDB, that worked best for us.
|
|
|
|