Link to home
Start Free TrialLog in
Avatar of mcseteach
mcseteachFlag for United States of America

asked on

Invalid object name master.dbo.spt_datatype_info

The issue we are experiencing is with cross database communication. We have a custom built solution (Golmine API, Triggers and Stored Procedures).

After we upgrade from Goldmine 6.7 (SQL Server 2000) to Goldmine 7.6(SQL Server 2008) our test user attempts to initiate a transfer between the two databases and receives the message “ Invalid object name 'master.dbo.spt_datatype_info' ”. After research it appears that this is a table that was retired by Microsoft between versions 2000 and 2005 of SQL server.

This is a mission critical application for us.  Any thoughts on how to resolve this issue would be greatly appreciated.
Avatar of devlab2012
devlab2012
Flag of India image

Set the compatibility mode of database to 2000. But be careful that if you new features of SQL 2008 will not be available in that case.
ASKER CERTIFIED SOLUTION
Avatar of GMGenius
GMGenius
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of mcseteach

ASKER

Thank you for the lilnk GMGenius.  We found a simular post in a different forum with the method to recreate the table but when our database admin attempted to use it he stated that it is missing a fixed length column and therefore did not perform properly.
I suppose the question next is, what are you using this data for?
Goldmine is used to work with potential students by Admissions.  Once they are accepted the information is sent from Goldmine to a campus wide CRM running on SQL2008.  Our current Goldmine is on SQL2000 and we would like to upgrade to a newer version running on SQL2008.

The stored procedures referencing the "expired" object are optional procedures that are used in conjuction with the Goldmine API. Apparently a standard installation of GM 6.7 does not contain references to the  retired object. This communication between databases was setup before my time here and there is little documentation.
I think the only option is to re-work the additional updates, perhaps the content can be copied here?