from the cs_CreateFullDatabase.sql, in cs_Wiki_UpdatePage procedure segment:
DECLARE @pagetags AS VARCHAR(MAX)
it's extend data type in sql2005... is 2008.5 sp1 imcompatible with sqlserver 2000?
There were three updates that need to occur for SQL Server 2000 installations. I have two files that I am adding to this reply that provide the appropriate update. One is for a new database install, the other is to update the schema patches and refresh the stored procedures. They are named as the original files + _sql2000 to differentiate from the originals. I am going to relay the changes here so you can updated your files yourself if you have a custom situation.
In schema patch 4.1.22:
EXECUTE sp_executesql N'ALTER TABLE [dbo].[cs_Wiki_PageRevisions]ADD [Tags] [nvarchar](4000) NOT NULL CONSTRAINT [DF_cs_Wiki_PageRevisions_Tags] DEFAULT ('''')'
In schema patch 4.1.26
EXECUTE sp_executesql N'IF OBJECT_ID(N''[dbo].[cs_Threads_Delete]'') IS NOT NULL exec sp_executesql N''DROP TRIGGER [dbo].[cs_Threads_Delete]'''
In dbo.cs_Wiki_UpdatePage, line 45
DECLARE @pagetags AS NVARCHAR(4000)
Thanks,David L. PentonThis posting is provided "AS IS" with no warranties, and confers no rights.
I only see two places in the SP1 upgrade script that require features beyond what is provided in SQL Server 2000. I don't have a SQL Server 2000 database server around anymore, but I suggest trying to replace the two entries (one is an NVARCHAR(MAX) column and the other is the VARCHAR(MAX) variable you refer to) with NVARCHAR(4000) and VARCHAR(8000) respectively.
If you're running CS 2008.5 on SQL Server 2000 now, then I think this may work for you.
Of course, back up your database and application before attempting the upgrade!
John Bledsoe
Sr. Software Specialist - ATGi
Thanks for bringing this to our attention! I've filed a new bug report (#1386).
I am experiencing the same problem in a customer project, which is stopping their upgrade. Is there any way to now any time line for when/if a fix will be available?
another imcompatible object: cs_CreateFullDatabase.sql, line 14860, in Patch: cs_Schema_Patch_4.1.26:
IF EXISTS (SELECT * FROM sys.triggers WHERE object_id = OBJECT_ID(N''[dbo].[cs_Threads_Delete]''))DROP TRIGGER [dbo].[cs_Threads_Delete]'
sys.triggers is the new object catalog view from sqlserver 2005. In Sqlserver 2000, error occurs:
Creating...cs_Schema_Patch_4.1.26Msg 208, Level 16, State 1, Line 2Invalid object name 'sys.triggers'
This issue sucks big time for us who are using SQL Server 2K as our DB backend. I was really looking forward to upgrade to CS 2008.5 but this issue is a big time bummer. Any updates on when a patch will be released?
Thanks!
Much of Telligent was off most of last week for Thanksgiving. I'm following up on this today and will try to post something back here shortly.
All,
We'll reply here with an update as soon as we have a reasonable resolution.
Thanks,David
thanks david.
i cleaned my db and performed new install with your patched script, no errors occurs.
the only effects should be the capacity of "page tags", it might not be a prob.
kenhwong,
Yes, you are correct.We consider that to be an acceptable risk - to minimize the updates to our codebase to make the SQL 2000 accommodation.
We've also updated the installation instructions to reflect this issue.
-Alex LoweCommunity Server, Evolution, and Harvest Documentation
my update error message, I don't know what's happen
伺服器: 訊息 207，層級 16，狀態 3，程序 cs_Wiki_GetPageRevision，行 10無效的資料行名稱 'Tags'。伺服器: 訊息 208，層級 16，狀態 11，行 2無效的物件名稱 'dbo.cs_Wiki_GetPageRevision'。Creating...cs_Wiki_GetPageRevisions伺服器: 訊息 207，層級 16，狀態 3，程序 cs_Wiki_GetPageRevisions，行 43無效的資料行名稱 'Tags'。伺服器: 訊息 208，層級 16，狀態 11，行 2無效的物件名稱 'dbo.cs_Wiki_GetPageRevisions'。
伺服器: 訊息 207，層級 16，狀態 1，程序 cs_Wiki_UpdatePage，行 47無效的資料行名稱 'Tags'。伺服器: 訊息 208，層級 16，狀態 11，行 2無效的物件名稱 'dbo.cs_Wiki_UpdatePage'。
Copyright© 2008 Telligent Systems Inc. All rights reserved CommunityServer.com • Telligent.com