Friday, February 10, 2012

Can I install SQL Server 2000 on machine which already have SQL Server 2000 ?

I need SQL server 2000 for one application and 2005 version for another.

Does SQL Server support multiple versions of software Install on the same windows server ?

Yes just install 2000 as a named instance, just make sure you have enough memory to keep all instances running. Hope this helps.|||

thanks..

Can I install SQL Server 2005 on machine which already have SQL Server 2000 ?

|||Yep just make it a named instance, the 2005 installer is much better because Microsoft reads my posts about installation. You may not run into issues if you need to use Reporting services you must have IIS installed and configured, this is important because Win2003 comes with IIS not installed and when you install it, it comes locked down. So if you need Reporting services post again and I will walk you through IIS configurations you need. Hope this helps.|||Yeah its possible to install..

If you installed sql2000 as default instance then you can install sql 2005 as named instance.
If you installed sql2000 as named instance then you can install sql 2005 as default instance.|||

Do you see any Microsoft paper or URLs about this kind of installation? Is it supported by Microsoft?

Also, can I have SQL 2000, SQL 2000 SP3, SQL 2000 SP4, SQL 2005 and SQL 7.0 on one server?

Thanks a lot.

Po-Shan.

MSN Messenger ID: poshanchang@.hotmail.com

Email: poshanchang@.yahoo.com

|||

If you installed sql2000 as default instance then you can install sql 2005 as named instance.
If you installed sql2000 as named instance then you can install sql 2005 as default instance.

Good.Are you sure about this ?

|||

Another Question:

What are changes we as DBA & Developer have to do when we migrate databases from default instance to Named Instance ?

Thanks

|||The only thing for developers is to change the connection string to point to the other instance, e.g. instead of Data Source=SomeServer it has to be Data Source=SomeServer\SomeInstanceName. Administrators have to (beside their normal work) make sure that the clients will reach the non default port (if configured as this) of the SQL Server service.

Jens K. Suessmeyer.

http://www.sqlserver2005.de

|||

Wondering why need different port numbers for each instance?

I thought the databases can be with the same port number, say 1433, and there could be many instances with this port on the same server, right?

As example,

SameServer\

SameServer\InstanceOne

SameServer\InstanceTwo

the three instances are all using 1433, right?

|||Yeah you can keep the default port for all the instances you install. By changing the port the app will easily detect its respective server and it will increase the security since hackers will first try for default port only.

No comments:

Post a Comment