October 30, 2015 at 2:54 am
Hello,
i had to move some sqlserver from one to another host.
So on the new host I installed sqlserver with the original Configuration.ini from the old host.
Then I copied the original temp, master, msdb, model and user databases to the new host.
Started everything and changed the hostname
sp_dropserver <old_name\instancename>;
GO
sp_addserver <new_name\instancename>, local;
GO
I thought that i was done. But then I found out that a configuration in the Agent wasn't activiated.
SQLServer Agent -> Properties -> Alert System -> Enable mail Profile
So why was this configuration not transferred?
Are there any other known configuration settings, which will not be transferred?
Is it somehow possible to generate a new Configuration.ini because some settings e.g. if I enable NamedPipes after the Installation, are lost on the new Installation?
thx for your answers
October 30, 2015 at 4:48 am
pod69 (10/30/2015)
Hello,i had to move some sqlserver from one to another host.
So on the new host I installed sqlserver with the original Configuration.ini from the old host.
Then I copied the original temp, master, msdb, model and user databases to the new host.
Started everything and changed the hostname
sp_dropserver <old_name\instancename>;
GO
sp_addserver <new_name\instancename>, local;
GO
I thought that i was done. But then I found out that a configuration in the Agent wasn't activiated.
SQLServer Agent -> Properties -> Alert System -> Enable mail Profile
So why was this configuration not transferred?
Are there any other known configuration settings, which will not be transferred?
Is it somehow possible to generate a new Configuration.ini because some settings e.g. if I enable NamedPipes after the Installation, are lost on the new Installation?
thx for your answers
Do not copy system databases between instances, it is not supported. There's a whole bunch of info that's buried in the master and msdb. Even if you kept the same servername and service account there's still a whole bunch of stuff that can cause issues.
Perform a clean migration of all objects to the new instance is your safest route.
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply