Pay attention to the problem of MSSQL view cross-Database Replication

A module of the Business System was developed yesterday. When copying and uploading a table and view of the test database to a work database, the copy Database Wizard was used to copy objects. An error occurred during view replication, the two view-related tables in the working database are immediately dropped, which is really painful.

I remember that I made the same mistake a few years ago and my website was suspended for two days.

Here, I would like to remind myself and everyone that the copy object function must be noted that the SQL view is different from the view in MDB, and the data in the view actually exists in the MSSQL database, when copying an object, the corresponding relationship between the view and the relevant table is re-created, resulting in the deletion of the original data table.