December 1, 2008 at 3:19 pm
hi,
We have a 32-bit windows 2003 standard edition and 32 bit SQL Server 2000 developer edition. Now,we are moving this instance to Sql server 2000 32 bit developer edition on Windows 2003 R2 enterprise editon.
On Xeon sql server 2000 64 bit is not supported,thats why we did as below
envoke setupsql.exe in x86 folder from the installation media.
Now can we follow the method 1 in this link http://support.microsoft.com/kb/246133
Or any other method is there for the above scenario?
December 1, 2008 at 3:43 pm
This is a SQL script, shouldn't matter if you have 32 or 64 bit.
December 1, 2008 at 5:49 pm
Thanks steve,
I installed the new sql server and it is in a different domain. After scripting the jobs from old server,what are the items do I need to change in the script before executing in the new server ?
thanks
December 2, 2008 at 12:16 pm
If you will be using different domain logins you should change those in the script before runing on the new box.
SQL logins would not be affected.
December 2, 2008 at 12:24 pm
Or set up a trust for the logins. This is more of a security issue that's the same as moving a file server to a new domain. Users need access or new accounts in the new domain.
December 2, 2008 at 12:34 pm
I had the issue when going to a new domain, unfortunately they would not set up a trust between the two (actually it was different forests), and so had to adjust the logins appropriately.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply