We have a few databases whose physical files are not in a standardized location. In a couple of databases the transaction log is stored in the same physical location as the main file. We would like to move them without breaking the applications that they serve.
From what I've read (so far) only SQL Server needs to know where these physical files are and as long as I get everything logged off and shut down nicely I should be able to Detach, move files, and re-attach w/o operational issues.
I did this to one of my simple test databases and it worked as expected. I then did this to a database that serves one of our applications and we had to call vendor support. They had to do some work on fixing various accounts.
I have 2 more to move and don't really want to go through that stress again. Can someone tell me if I'm likely to run into problems each time I do this? I've read many good SQL books that explain how to do this and none of them warn of any consequences