April 26, 2007 at 7:19 am
Hi
We are moving our databases from an old server to a new server. We are trying to kill two birds with one stone since the person that orginally installed SQL Server on the old server installed personal edition.
We are doing the data move ny mirroring the directory structures and moving the data and log files including the system dbs.*
* with the exception of scripting out the jobs and deleting them from the old server first and recsripting them to the new server
the problem is that the new server now thinks that it is running personal edition since I assume the edition info is stored somewhere in the old master db
Is there any quick resolution to this ?
April 26, 2007 at 11:52 am
Have you installed Standard edition on the new server? You'll have to do that before moving anything from the old server.
Greg
Greg
April 26, 2007 at 12:14 pm
You can't "upgrade", but you can detach the dbs from personal and attach to Standard. As mentioned above, install only Standard on the new server.
April 26, 2007 at 12:30 pm
Hi Yes,
Standard is installed on the new server. The old server has since been decommissioned, but when select the version number and edition SQL Server tells me that I am running Personal edition on the new server despite installing standard. Is this because I copied the master db from the old server and overwrote the master on the new server
Cheers
Simon
April 27, 2007 at 10:02 am
I think that info is stored in master. You can see it in the system table spt_server_info.
As for fixing it, one thing that comes to mind is to backup or detach the user databases, script out logins, jobs, and DTS packages, uninstall and reinstall SQL Server Standard Edition, restore or attach user databases.
Alternatively, you could investigate the Rebuild Master utility. It will recreate master, msdb, and model.
Greg
Greg
April 27, 2007 at 5:15 pm
Hi Greg,
Yes the logins are my main concern, scripting out the logins would mean a new password for all of the database users. Of course this wouldn't be an issue if we still had the old DB in which case we could do a transfer logins DTS task 😉
Rebuilding the master sounds a promising bet I'll give that a try first
Cheers
Simon
April 30, 2007 at 9:28 am
Simon,
You can script out SQL Server logins with their passwords. I've used sp_help_revelogin, as described in this article http://support.microsoft.com/kb/246133/en-us, many times. Next time, eh?
Greg
Greg
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply