sysmessages table issue

This is the expected behavior for system compatibility views from SQL Server 2012+:

When referenced in a user database, system tables which were announced as deprecated in SQL Server 2000 (such as syslanguages or syscacheobjects), are now bound to the back-compatibility view in the sys schema. Since the SQL Server 2000 system tables have been deprecated for multiple versions, this change is not considered a breaking change.

Example: If a user creates a user-table called syslanguages in a user-database, in SQL Server 2008, the statement SELECT * from dbo.syslanguages; in that database would return the values from the user table. Beginning in SQL Server 2012, this practice will return data from the system view sys.syslanguages.

You're probably going to have to fix your database to not use the same names as deprecated system tables (now system views in the sys schema).

Tags:

Sql Server

Sql Server 2016

Related

When the primary key is also the foreign key, in Postgres What events still occur within a transaction that gets rolled back? Why do we have Top N Sort in this example? SQL Server - Snapshot is useful in production environments? Does timestamp protocol following thomas's write rule allow non-view-serializable schedules in some cases? Does SQL Server Only Perform Calculations In A SELECT List Once? How to make sure change_tracking statistics stays updated Is there an operator or an easy way to match an expression one or more times with the LIKE operator in SQL? During a log backup is the data backed up to the start or end of the operation? How SQL Server caches data in memory How is calculated fill-factor percentage related to size of database? Why is it not recommended to use RAID 5 for a log file?

Recent Posts