January 12, 2009 at 12:36 pm
Hello folks,
I am being tasked to help move windows2003/SqlServer2005 apps to a windows2008/SqlServer2008 server. Ultimately the new server and its updated DBMS will be a replacement for the 2005 server.
As I have always been more involved in development than administration I have a few questions...
Situation) The old 2005 sql server exists in a windows workgroups network, and the new server will be a part of our new domain, as we are just now going to active directory. It was my intention to label the machine name of the new server the same as the old server, and to do the same for the SQL Server instance. I was doing this in case any of the 2005 apps called for objects based on machine-name/sql server instance names.
Question) Will having two machines with the same machine name, and sql server named instance cause any problems right out of the gate? Is this a bad idea for some reason I have yet to understand?
Question) Are their any other tips that have come to be commonly recognized as good advice when doing something similar to what I described above - that is four fold: 1) moving to a new server, 2) moving to the latest DBMS, & lastly 3) moving to Active Directory?
Thanks in advance for your thoughts!
regards,
-Matt G.
January 12, 2009 at 12:45 pm
Since the server with same name is in different domain you should not see any issue. My manager had asked me to upgrade one 2005 production server to SQL Server 2008 and I had asked him to wait for another couple of months so that MS would come with SP2. MS always had the tendency of giving service packs and it's always good to upgrade at least by SP2 in market.
For other question, not an issue and you can upgrade and keep an eye on regular patches from MS.
SQL DBA.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply