I pass this along from one of my administrators.

Subject: Please post to ADSM listserve


We are running Microsoft SQL Server 7.0 on a Microsoft Cluster (NT 4.0
EE); backing up the machine files and shared storage with TSM 3.7.2 and
the SQL databases with TDP 1.1.2.  In the past I have used TDP 1.1.2 to
backup SQL 7 databases on a standalone server, SQL 7 databases on a
clustered server, SQL 6.5 databases on both standalone and clustered servers.

Recently we upgraded an existing MSSQL 6.5 server to MSSQL 7.0 server.  If
you check the backwards compatibility level on each database, you will see
that the user-defined databases are at compatibility-level 65 and the
system databases are at compatibility-level 70.  All databases backup
successfully with TDP 1.1.2 regardless of compatibility level.  We then
copied that MSSQL 7.0 server's databases onto a clustered MSSQL 7.0 server
using the backup / restore method for data copying.  Now -- on this
clustered server -- TDP cannot backup any databases at compatibility level
65.  If I manually change a database's compatibility level to 70, TDP will
back it up.  Once I change it back to comp-level 65, TDP errors out with a
message:  "Client ended transaction:  DB-LIB error:  Incorrect syntax near
keyword 'database'."

Has anyone else experienced this behavior on a clustered MS SQL
Server?  For the sake of the app, the user-defined databases must be
maintained at compatibility level 65.

Fred Johanson
System Administrator, ADSM
S.E.A.
University of Chicago
773-702-8464