Non-Liferay tables are upgraded

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 6.1.0 CE GA1, 6.1.10 EE GA1, 6.2.0 CE M2
• Fix Version/s: 6.1.20 EE GA2, --Sprint 11/12, 6.2.0 CE M2
• Component/s: Upgrades
• Labels:
  • QA-R
• Environment: SQL Server 2008, Tomcat
• Branch Version/s:
  6.1.x
• Backported to Branch:
  Committed
• Similar Issues: Show 4 results ; ;

  LPS-11178	VerifyMySQL() alters non Liferay tables
  LPS-29479	Non-Liferay tables upgraded on Oracle
  LPS-4817	Fix incorrect upgrade tables
  LPS-27292	Add create table script for Journal Folder in upgrade process

If there are SQL Server System Tables present in a database, Liferay will sometimes try to upgrade the pseudo-system database table and will throw an error.

Steps to reproduce:
1. Need pseudo-system tables in the database System Tables section
This can be done by setting up some kind of system database mail.
2. Upgrade

Liferay will try to upgrade it and get a messaged like:

15:38:03,231 INFO [VerifySQLServer:130] Updating sysmail_mailitems.recipients to use nvarchar
15:38:03,262 ERROR [VerifySQLServer:88] java.sql.SQLException: Incorrect syntax near ')'.
java.sql.SQLException: Incorrect syntax near ')'.

sysmail_mailitems is not a Liferay table.

depending on the tables present, other sys tables will be upgraded.

Possible solution is to update the filter that determines which tables to alter and have it include 'AND (sysobjects.category != 2)' as pseudo-system tables have that category value.

http://social.msdn.microsoft.com/Forums/zh/sqlreplication/thread/135ec547-2214-4da3-bd42-5c458759e144