text/microsoft-resx 2.0 System.Resources.ResXResourceReader, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 Unqualified Join(s) detected Warning Starting with database compatibility level 90 and higher, in rare occasions, the 'unqualified join' syntax can cause 'missing join predicate' warnings, leading to long running queries. Use explicit JOIN syntax in all cases. SQL Server supports the below explicit joins: LEFT OUTER JOIN or LEFT JOIN, RIGHT OUTER JOIN or RIGHT JOIN, FULL OUTER JOIN or FULL JOIN, INNER JOIN. Deprecation of "Old Style" JOIN Syntax https://go.microsoft.com/fwlink/?LinkId=798568 Syntax issue on the source server Warning While parsing the objects on the source database, one or more syntax issues were found. Syntax issues on the source database indicate that some objects contain unsupported syntax in the server version and database compatibility level. Review the list of objects and issues reported, fix the syntax errors, and re-run assessment before migrating this database. ORDER BY specifies integer ordinal Warning Order the result set of a query by the specified column list and, optionally, limit the rows returned to a specified range. The order in which rows are returned in a result set are not guaranteed unless an ORDER BY clause is specified.,"Specify the sort column as a name or column alias rather than hard coding the ordinal. This rule checks stored procedures, functions, views and triggers for use of ORDER BY clause specifying ordinal column numbers as sort columns. A sort column can be specified as a nonnegative integer representing the position of the name or alias in the select list, but this is not recommended. An integer cannot be specified when the order_by_expression appears in a ranking function. A sort column can include an expression But when the database is in SQL 90 compatibility mode or higher, the expression cannot resolve to a constant. https://docs.microsoft.com/en-us/sql/t-sql/queries/select-order-by-clause-transact-sql?view=sql-server-ver15 BACKUP LOG WITH NO_LOG|TRUNCATE_ONLY statements are not supported Warning Backing Up the Transaction Log (full and bulk-logged recovery models) Remove BACKUP LOG WITH NO_LOG|TRUNCATE_ONLY statements from scripts. Microsoft highly recommends to set your database recovery to FULL recovery mode and perform regular transactional log backups to prevent the log from growing too big. If you do not need point-in-time recovery, switch to SIMPLE recovery mode. Assessment detected BACKUP LOG WITH NO_LOG|TRUNCATE_ONLY statements. These backup/restore options are not supported anymore. BACKUP (Transact-SQL) https://go.microsoft.com/fwlink/?LinkID=698472 Remove the use of PASSWORD in BACKUP command Warning Some of the detected BACKUP command options have been deprecated or discontinued such as, BACKUP { DATABASE | LOG } WITH PASSWORD and BACKUP { DATABASE | LOG } WITH MEDIAPASSWORD. Remove the use of BACKUP { DATABASE | LOG } WITH PASSWORD and BACKUP { DATABASE | LOG } WITH MEDIAPASSWORD commands. Replace them with the currently supported BACKUP command syntax. This syntax should not be used for creating future restore scripts. See BACKUP (Transact-SQL) https://go.microsoft.com/fwlink/?LinkId=798527 Deprecated data types TEXT, IMAGE or NTEXT Warning These data types are checked as deprecated. In some cases, using TEXT, IMAGE or NTEXT might harm performance. Deprecated data types are marked to be discontinued on next versions of SQL Server, should use new data types such as: (varchar(max), nvarchar(max), varbinary(max) and etc.) ntext, text, and image (Transact-SQL) https://go.microsoft.com/fwlink/?LinkId=798558 Constant expressions are not allowed in the ORDER BY clause in 90 or later compatibility modes Error Constant expressions are allowed (and ignored) in the ORDER BY clause when the database compatibility mode is set to 80 or earlier. However, these expressions in the ORDER BY clause will cause the statement to fail when the database compatibility mode is set to 90 or later.Here is an example of such problematic statements:SELECT * FROM Production.ProductORDER BY CASE WHEN 1=2 THEN 3 ELSE 2 END Before you change the database compatibility mode to 90 or later, modify statements that use constant expressions in the ORDER BY clause to use a column name or column alias, or a nonnegative integer representing the position of the name or alias in the select list. Remove user-defined type (UDT)s named after the reserved GEOMETRY and GEOGRAPHY data types. Warning Microsoft SQL Server introduced new data types GEOMETRY and GEOGRAPHY for storing "Spatial Data". The terms used for spatial data types should not be used as names for either common language runtime (CLR) or alias UDTs. Remove UDTs named after the reserved GEOMETRY and GEOGRAPHY data types. Remove UDTs named after the reserved GEOMETRY and GEOGRAPHY data types https://go.microsoft.com/fwlink/?LinkID=724415 FOR BROWSE is not allowed in views in 90 or later compatibility modes Warning The FOR BROWSE clause is allowed (and ignored) in views when the database compatibility mode is set to 80. The FOR BROWSE clause is not allowed in views when the database compatibility mode is set to 90 or later. Before you change the database compatibility mode to 90 or later, remove the FOR BROWSE clause from view definitions. See FOR BROWSE https://docs.microsoft.com/en-us/sql/t-sql/queries/select-for-clause-transact-sql?view=sql-server-ver15#for-browse WITH CHECK OPTION is not supported in views that contain TOP in compatibility mode 90 and above Warning Assessment detected a view that uses the WITH CHECK OPTION and a TOP clause in the SELECT statement of the view or in a referenced view. Views defined this way incorrectly allow data to be modified through the view and may produce inaccurate results when the database compatibility mode is set to 80 and earlier. Data cannot be inserted or updated through a view that uses WITH CHECK OPTION when the view or a referenced view uses the TOP clause and the database compatibility mode is set to 90 or later. Modify views that use both WITH CHECK OPTION and TOP if data modification through the view is required. FOR XML AUTO queries return derived table references in 90 or later compatibility modes Warning When the database compatibility level is set to 90 or later, FOR XML queries that execute in AUTO mode return references to derived table aliases. When the compatibility level is set to 80, FOR XML AUTO queries return references to the base tables that define a derived table. For example, the following query, which includes a derived table, produces different results under compatibility levels 80, 90, or later:SELECT * FROM(SELECT a.id AS a, b.id AS bFROM Test a JOIN Test b ON a.id=b.id) AS DerivedTest FOR XML AUTO;Under compatibility level 80, the query returns the following results. The results reference the base table aliases a and b of the derived table instead of the derived table alias.<a a="1"><b b="1"/></a><a a="2"><b b="2"/></a>Under compatibility level 90 or later, the query returns references to the derived table alias DerivedTest instead of to the derived table's base tables.<DerivedTest a="1" b="1"/><DerivedTest a="2" b="2"/> Modify your application as required to account for the changes in results of FOR XML AUTO queries that include derived tables and that run under compatibility level 90 or later. Discontinued DBCC commands referenced in your T-SQL objects Warning Many DBCC commands that were available in prior releases have been replaced with DMVs and DMFs, or no longer exist; therefore, using these commands may cause errors and unforeseen effects after upgrading your SQL Server. Re-write the code, replace \DBCC DBREINDEX\" with \"ALTER INDEX\" with \"REBUILD\" option. Re-write the code replace \"DBCC INDEXDEFRAG\" with \"ALTER INDEX\" with \"REORGANIZE\" option.Re-write the code replace \"DBCC SHOWCONTIG\" with \"sys.dm_db_index_physical_stats\". Use of DBCC PINTABLE/DBCC UNPINTABLE is not required and has been removed to prevent additional problems. The syntax for this command still works but does not affect the server. Refer to SQL Server books online for equivalent DMVs and DMFs that you may want to use instead of deprecated and discontinued DBCC commands." Deprecated Database Engine Features in SQL Server https://go.microsoft.com/fwlink/?LinkID=698477