Post reply

SQL Server retaining extinct link to external HDD

  • March 8, 2007 at 6:49 pm

    #117890

    I recently used SQL Server to rationalise a very large data set from a client into an online inventory. For convenience, the raw data was in one database - kept on an external hard drive (300Gb). The final result was transferred to a seperate database which was stored on a local drive.

    Now I have noticed that SQL Server Service Manager will not start my service unless the external hard drive is connected. I have removed the 'raw' database (which lived on the external HDD) from from SQL Server Group, but SQL Server still strangely needs connectivity to the external drive.

    I'm running SQL Server Enterprise Manager v8.0.

    Anyone else had a similar problem or can suggest a solution?

  • March 12, 2007 at 8:00 am

    This was removed by the editor as SPAM

  • March 13, 2007 at 8:38 am

    #694710

    Do you have any startup paramaters that try to look at that drive, or have the default data or log location set to a location on that drive?

    The Redneck DBA

  • March 13, 2007 at 8:56 pm

    #694846

    Thanks Jason - it was the tempdb.  I'd moved it to the external hard drive at the same time I created the inventory database.  So on startup, SQL Server was trying to connec to the external HDD for the temp log etc each time, not trying to find the extinct database.

    For reference of anyone searching, attached is the SQL to move tempdb

    use master

    go

    Alter database tempdb modify file (name = tempdev, filename = 'C:\temp\tempdb.mdf')

    go

    Alter database tempdb modify file (name = templog, filename = 'C:\temp\templog.ldf')

    Go

    which moved my tempdb to C:\temp

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply