1. the backup function of sqlserver was used as early as possible, which can be implemented locally. ProgramCall. When the VM cannot be sent, the VM closes most of the stored procedures. You have to consider using other methods.
2. Later, I used my own stored procedure to back up the database. At that time, the VM and database were on the same machine, and OK was okay.
3. Due to speed issues, the VM must be moved to Hong Kong. Therefore, the second method cannot be implemented.
I want to come and try it out. Hey hey, use the local sqlserver.
Create a new package, click "Copy sqlserver object task", and enter the source/destination/copy information. In general, if the data volume is small, we can replace the existing data, which is also the most normal situation. I think this is feasible. If it is an append, the modified information will be lost. Then, the SQL server of the VM generally requires a user name and password, so we will add the same user name and password in the security of our local SQL Server. In this way, there will be no problems during execution.
Then we save the package and make sure that the SQLAgent service has been started. If it starts, right-click the package we just created in data conversion service-local package, and select scheduling. Set a time period. I usually choose 12 o'clock. At that time, everyone went to dinner ~~
The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion;
products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the
content of the page makes you feel confusing, please write us an email, we will handle the problem
within 5 days after receiving your email.
If you find any instances of plagiarism from the community, please send an email to:
info-contact@alibabacloud.com
and provide relevant evidence. A staff member will contact you within 5 working days.
