Are the table schema and database file structure changes propagated to the secondary server?
A7: In SQL Server 2000, all table schema and database file structure changes are logged operations. However, if a new NDF or LDF file is added to the primary database, the transaction log restore job fails while loading the transaction log backup that was performed immediately after the database file was added to the primary database.
Related Questions
- Is it possible to generate a database schema in Oracle using a script with CREATE TABLE, from an XML file generated by a Rational Rose design tool?
- Are the table schema and database file structure changes propagated to the secondary server?
- Can table structure changes be made on a live (in production) database with users connected?