January 9, 2008 at 12:36 am
Hi!
Since the 21'st of december last year (at least thats the earliest time we know for sure the problem started) all new tables created in any db on a certain server gets the property IsMSShipped set to true.
Does anyone know how this can happen?
This means we can create, alter, drop etc tables as usual, but we cant use sp_rename on table columns (this is so far the only thing we noticed that does not work as usual).
It does not matter if we create a new database and create tables in that db, tables are still created with this property set.
Testcode:
CREATE TABLE t_test(a INT)
SELECT OBJECTPROPERTY(OBJECT_ID('t_test'), 'IsMSShipped')
EXEC SP_RENAME 't_test.a', 'e', 'COLUMN'
DROP TABLE t_test
GO
Returns:
-----------
1
(1 row(s) affected)
Msg 15001, Level 16, State 1, Procedure sp_rename, Line 310
Object 't_test.a' does not exist or is not a valid object for this operation.
Any hints on the topic would be highly appreciated!
cheers
/Linus
January 9, 2008 at 1:07 am
Problem seems to be solved. Apparently, the server can be set in this mode with:
EXEC master.dbo.sp_MS_upd_sysobj_category 1
and restored with
EXEC master.dbo.sp_MS_upd_sysobj_category 2
see:
http://www.dbforums.com/archive/index.php/t-356511.html
cheers and thanks for reading 🙂
/Linus
January 9, 2008 at 1:20 am
thanks for the info
"Keep Trying"
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply