May 27, 2009 at 5:19 am
We have recentley updated our compat level to 90 on a prod database. We have setup snapshot replication from SQL 2005 box to SQL 2000 as a push subscrription (only one allowed). This has been working fine, until we altered the comp level to 90, now the scripts that are being generated *.sch contain invalid sysntax for sql 2000 - i.e. CREATE TYPE for creating user defined datatypes. And create tables using those datatypes are being created using [dbo].[UserDefinedTypeName] so i have had to manually alter a load of scripts...
but tomorrow it will happen again, so how can i set it to generate sql 2000 compatible scripts?
Oraculum
May 27, 2009 at 6:15 am
oraculum (5/27/2009)
We have recentley updated our compat level to 90 on a prod database. We have setup snapshot replication from SQL 2005 box to SQL 2000 as a push subscrription (only one allowed). This has been working fine, until we altered the comp level to 90, now the scripts that are being generated *.sch contain invalid sysntax for sql 2000 - i.e. CREATE TYPE for creating user defined datatypes. And create tables using those datatypes are being created using [dbo].[UserDefinedTypeName] so i have had to manually alter a load of scripts...but tomorrow it will happen again, so how can i set it to generate sql 2000 compatible scripts?
In merge replication you can set your compatibility level. Not in transactional. I don't know about snapshot. If you can I would start there. If not, set the database back. Not many options outside of that I don't think.
David
@SQLTentmaker“He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply