SQL 6.5 and SQL 7.0 Simultaneously Active on Same Host

[Andrew Dominguez]

Has anyone developed a workaround to have SQL 6.5 and SQL 7.0 simultaneously active on the same NT 4.0 Server host. The use of VSWITCH.EXE to switch between SQL 6.5 and SQL 7.0 in not an acceptable solution. There are several applications that are only supported under SQL 6.5 and will not be upgraded to SQL 7.0 for another 3 to 6 months.

There are other applications (ERP and data mart) that were developed specifically for SQL 7.0 to take advantage of its new DTS, OLAP, and query capabilities.

All these applications need full-time access to their respective databases.

The obvious solution is to host SQL 6.5 and SQL 7.0 on separate servers. The client has a "monster" database server which would be too expensive to duplicate. Using a "standard" PC to host SQL 6.5 would significantly compromise performance of those applications.

Any advice or suggestions would be appreciated.

Andrew Dominguez, IMS
ajd@cwix.com
909.625.4066 / 7826 fax

[Gert Drapers]

Why can't you run all your databases on 7.0 and set the sp_dbcmptlevel of the database that need to run in 6.5 mode to 6.5 ? SQL Server 7.0 support compatibility mode just because of that reason. Did you try that ? Any reason why that would not be a solution ? Problems ?

-GertD
gertd@cohesion-software.com

[Jonathan Yang]

I remember somebody's answer to the same question in this forum:
"You are plying with fire."

Jonathan

------------
Andrew Dominguez at 3/26/99 8:37:10 AM

Has anyone developed a workaround to have SQL 6.5 and SQL 7.0 simultaneously active on the same NT 4.0 Server host. The use of VSWITCH.EXE to switch between SQL 6.5 and SQL 7.0 in not an acceptable solution. There are several applications that are only supported under SQL 6.5 and will not be upgraded to SQL 7.0 for another 3 to 6 months.

There are other applications (ERP and data mart) that were developed specifically for SQL 7.0 to take advantage of its new DTS, OLAP, and query capabilities.

All these applications need full-time access to their respective databases.

The obvious solution is to host SQL 6.5 and SQL 7.0 on separate servers. The client has a "monster" database server which would be too expensive to duplicate. Using a "standard" PC to host SQL 6.5 would significantly compromise performance of those applications.

Any advice or suggestions would be appreciated.

Andrew Dominguez, IMS
ajd@cwix.com
909.625.4066 / 7826 fax

[Andrew Dominguez]

Haven't given your approach a try yet but have already noticed differences like the absence of a segment column in the SQL 7.0 sysindexes table which existed in SQL 6.5

I'll run the sp_dbcmptlevel for 6.5 mode and see if this does the job. Thanks for the reply.

Andrew Dominguez


------------
Gert Drapers at 3/28/99 3:47:15 PM

Why can't you run all your databases on 7.0 and set the sp_dbcmptlevel of the database that need to run in 6.5 mode to 6.5 ? SQL Server 7.0 support compatibility mode just because of that reason. Did you try that ? Any reason why that would not be a solution ? Problems ?

-GertD
gertd@cohesion-software.com