Microsoft SQL Server Management Studio is a client tool for SQL Server, which I believe you all know. I don't know how the guys use the import data, but I've met them recently. The main reason is that there is no permission to the remote database server, and you need to test the conflict between the new modified content and the old data. Because of the process changes, it is unavoidable to modify the data to adapt to the new changes. So you need to simulate real-world data in a test environment. It was also funny, just paste it into Excel and then copy it to the database. In general, this is also possible, but for some special characters, if you paste directly into Excel, it can not be displayed normally, such as bit fields, datetime fields.
I wonder if everyone knows that Microsoft has provided us with the ability to import and export data. The following is directly attached to the procedure, because it is also relatively simple, so there is no special need to explain. Refer directly to the following figure:
The following map and a simple description, to import data As an example, the export data function as if the import data exactly the same, do not know why two to get out.
The following illustration also shows that selecting the source from which you want to copy data , that is, setting source data, such as copying from A to B, is the database for setting a.
Then it says copy from A to B, and the following figure is the database to set B
The following figure provides two ways to select a replicated data source, if a is the same structure as B, select the first method, and the other is to personalize the data source that you want to copy
Because the demo database (a in the example above) has only one table, the following figure shows only a table, if there are more than one table, it will be displayed, tick the table we need to copy
Note: What you need to explain here is that if the table in a uses the primary key is the way to grow, then you need to put the table in B from the growth of the way first removed. Because copying from A to B is a copy of all the fields, including the self growing ID, it needs to be replicated as well. After the data is copied, the table that is changed back to the B database is the self-growth mode.