What are the challenges you face when working across database platforms? Take the survey
Options

Version 3.8 not compatible with SQL Server 7.0?

JoshCohenJoshCohen Posts: 7
I just upgraded from SQL Prompt version 3.6 to 3.8. Now it gives an error when trying to retrieve the database schema from a 7.0 server (still works OK on SQL Server 2000):

Unable to refresh or cache database <servername.databasename> due to the following error: 'IDENT_CURRENT' is not a recognized function name.
Line 49: Incorrect syntax near 'ftjoin'..

RedGate.SqlPrompt.Engine.Cache.DatabaseRefreshException: Unable to refresh or cache database <servername.databasename> due to the following error: 'IDENT_CURRENT' is not a recognized function name.
Line 49: Incorrect syntax near 'ftjoin'.. ---> System.Data.SqlClient.SqlException: 'IDENT_CURRENT' is not a recognized function name.
Line 49: Incorrect syntax near 'ftjoin'.
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlDataReader.ConsumeMetaData()
at System.Data.SqlClient.SqlDataReader.get_MetaData()
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader()
at k.p(SqlConnection )
at k.a(j )
at RedGate.SQLCompare.Engine.Database.RegisterForSqlPrompt(ConnectionProperties connectionProperties, Options options, Boolean includeSystemObjects)
at cy.b(IAuthenticationTokenProvider )
--- End of inner exception stack trace ---
at cy.b(IAuthenticationTokenProvider )
at cy.a(Exception , Database , IAuthenticationTokenProvider )
at cy.a(IAuthenticationTokenProvider )
at cy.GetMetaData(IAuthenticationTokenProvider provider)
at M.b(G , IAuthenticationTokenProvider , Boolean , EventHandler`1 , EventHandler`1 , EventHandler`1 , EventHandler`1 )

Comments

  • Options
    Hi there,

    I'm afraid that SQL Server 7 is not a supported platform anymore. The latest engine for SQL Prompt now needs to support SQL Server 2008 and we have to draw the line somewhere. Sorry,

    Tom
  • Options
    Having updated my 3.6 installation to 3.8 I have encounted the same problem as Josh. As my organisation has two SQL 7 boxes running (one production, one dev), I have uninstalled 3.8 and gone back to 3.6.

    I wonder how many other "roll-backs" will be undertaken? I suspect we are not alone in still running SQL 7.0 (which is still under extended support until 2011 - http://support.microsoft.com/lifecycle/?p1=2862)

    Did Red Gate conduct a landscape survey before deciding to pull support for SQL 7.0?
Sign In or Register to comment.