0

First I am not a SQL DB. I inherited an old system and am trying to keep the wheels from falling off.

We have an MS SQL 2000 server (running server Win Server 2000) that we performed a P2V migration on. I did not realize that there are temp files running on an external USB HDD (that was connected to the old physical server) necessary for SQL operations.

Its looking like we can not connect the USB HDDs to the VM (due to age of the OS, and the HDD being a 3.0, doesnt look like VMWare supports 3.0 passthrough to Win Server2000).

So, is it possible to set those external HDDs up as a shared drive on another machine and run those temp SQL operations from the VM? As it is now the DB looks for a physical drive volume. We are considering swapping out the HDDs to USB 2.0, but this seems more time efficient. Thanks for any input

5
  • In general, you can put TempDB anywhere you want. It could be an existing drive on the VM (not great, but OK as a stopgap measure), or a new virtual drive, or a non-local drive (again, not a great idea). This might help: brentozar.com/archive/2017/11/move-tempdb-another-drive-folder
    – Doug Deden
    Commented Apr 14, 2021 at 20:01
  • 3
    Also, run (don't walk) to your boss and let them know that both SQL 2000 and Windows 2000 are out of support, and have been for a long time. You are open to security vulnerabilities, performance risks, and reliability concerns. Do whatever you need to to make your boss realize that you can't provide good business value on unsupported software.
    – Doug Deden
    Commented Apr 14, 2021 at 20:04
  • legacy can be a bich, but wmware can map drivesm and for the hist system it doesn't matter id scsi,usb or sata, so map them and bind themto the image
    – nbk
    Commented Apr 14, 2021 at 22:38
  • @DougDeden - this was super helpful. worked like a champ. I executed the move TempDB process and things seem to be running as they should. As for your other point, that is exactly what I am working. thanks for the input!
    – mcv110
    Commented Apr 15, 2021 at 14:01
  • 1
    Then upvote and accept @DougDeden's answer. Commented Apr 15, 2021 at 15:31

1 Answer 1

1

In general, you can put TempDB anywhere you want. It could be an existing drive on the VM (not great, but OK as a stopgap measure), or a new virtual drive, or a non-local drive (again, not a great idea).

There are a lot of references on the Internet for how to relocate TempDB. And for how to start SQL if the current TempDB is not accessible. Here are some good ones:

Also, run (don't walk) to your boss and let them know that both SQL 2000 and Windows 2000 are out of support, and have been for a long time. You are open to security vulnerabilities, performance risks, and reliability concerns. Do whatever you need to to make your boss realize that you can't provide good business value on unsupported software.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.