March 27, 2015 at 10:13 am
If I run an ALTER DATABASE command that renames the Logical file name of a database, will I run into any unseen consequences in terms of day to day use of the database?
March 27, 2015 at 10:22 am
I didn't even know you could do that. Can I ask why you want to, please? I can't think of any problems it would cause, since your applications don't care what the names of the database files are.
John
March 27, 2015 at 10:25 am
John Mitchell-245523 (3/27/2015)
I didn't even know you could do that. Can I ask why you want to, please? I can't think of any problems it would cause, since your applications don't care what the names of the database files are.John
OCD, to be honest. But it has been requested of me in the past and I said I'd look into it. I've tested this on a non-used dev database with good results, but I am apprehensive to run it in Prod. Personally, I can overlook the "problem" but others won't unless I can give them good reason NOT to do this.
March 27, 2015 at 11:09 am
certain operations rely on the logical filename but mostly system stuff. It's a good practice to ensure your logical filenames are unique, having 100 databases on the server all with same logical filenames could get confusing at the least
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
March 27, 2015 at 12:10 pm
Perry Whittle (3/27/2015)
certain operations rely on the logical filename but mostly system stuff. It's a good practice to ensure your logical filenames are unique, having 100 databases on the server all with same logical filenames could get confusing at the least
Good enough for me. Thanks.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply