How to solve missing schema issues in scripts for databases with SQL Server 2000 compatibility (4213589)

Applies to
ApexSQL Script

Summary
This article describes how to create correct scripts with ApexSQL Script for objects that contain schemas other than dbo

Cause
As schemas are first introduced in SQL Server 2005, they are neither scripted nor shown in Object filter for databases with SQL Server 2000 compatibility

Schemas also don’t show up as dependent objects in the Script wizard

Resolution
To fix this problem, change the database compatibility level from SQL Server 2000 to SQL Server 2005 or higher

See also
ALTER DATABASE Compatibility Level (Transact-SQL)

About ApexSQL Script
ApexSQL Script generates scripts for SQL Server database objects and data Script SQL databases to source control, generate .NET executable and C# projects for deployment, and automate script generation using CLI

Last updated
April 7, 2013