Existing database maintenance plans are upgraded and continue to work in SQL Server 2005. However, you will not be able to create new database maintenance plans by using SQL Server Management Studio. To view the maintenance plans in Object Explorer, expand Management, and then expand Legacy. You can migrate existing database maintenance plans to the new format by selecting Migrate from the context menu for any database maintenance plan. Because the new maintenance plan feature is not a direct replacement of database maintenance plans, some functionality might be lost after migration. Migrating a database maintenance plan does not delete the old plan, so you can test its functionality as a maintenance plan before removing the old plan.
Exhaustive search of '%1!s!' (database ID %2!s!) for inconsistencies failed due to exception %3!s!, state %4!s!. This is ...
Existing clustered and nonclustered indexes must be left intact in the database. All other structures will be removed from ...
Existing clustered indexes must be left intact in the database. All other structures will be removed from the database, however. ...
Existing configuration information in configuration table for specified connection name will be overwritten with new configuration ...
Existing database maintenance plans are upgraded and continue to work in SQL Server 2005. However, you will not be able to ...
Existing Meta Data Services packages should be moved to SQL Server storage (in the msdb database) or to structured storage ...
Existing partition-aligned structures must retain their partitioning. Any recommended new structures will align with the ...
Existing SQL Agent user proxy accounts will be upgraded to a single new proxy called UpgradedProxyAccount. By default, all ...
EXISTS=3=Subselect=The Exists function returns true if the SELECT statement specified as its argument returns one or more ...