A good customer wants to establish VSS

If regular changes are made during the design and the data is not officially used, it can be said that VSS is not easy to establish, but there is no reason for customers to switch to maintenance.

Failure to build: the possibility of errors caused by hasty changes is extremely high. After each change, the system is worried. When others ask, they can't tell the specific changes;

To create a VSS instance, follow these steps: Set the database location, directory, File Import directory, and set VSS startup in Visual Basic.

Several principles should be taken into consideration: 1) The entire process will not be lost due to disk C formatting; 2) Development on each machine; 3) Unified login accounts. Do not use this account today, using that account tomorrow will cause the file to get stuck again.

In fact, what I pay the most attention to is the Historical Comparison Feature of VSS. This way, the Historical Comparison Feature may detail the changes. However, VSS cannot be directly controlled for databases, views, and stored procedures. Is there any good way? For example, each time we export an archive.

From the perspective of using VSS in clcon, there are some problems: the loss of VSS information in disk C format;