I have been in contact with ZBLOG for many years. At first, I paid attention to Moonlight Blog. I was very friendly to his sharing spirit and the quality of his blog. Therefore, I also liked this program of ZBLOG. It’s been a bit of a heartache, but after all, I’m not a professional, so I still only know the skin and don’t understand the in-depth technology for many technical problems.
What I want to share with you today is the experience of using the SQL SERVER2012 database. We know that the ACCESS database is not powerful enough in terms of data processing capabilities and limited in efficiency, so I was forced to think about changing the database.
Relevant data and materials: domain name (post- reading blog created by ZBLOG , new site web actual combat, welcome to make comments and learn and progress together!), ASP program + MS-SQL database, belonging to educational learning sites.
Let's share the operation steps and some precautions for upgrading from ACCESS to sql server2012 database:
1. Back up the database. Before upgrading and converting, you must pay attention to protecting your data. This is the most important thing. In case of operation mistakes, there is still a chance to restore.
2. Install sql server2012 on the server, the installation process is generally not smooth, you can refer to some tutorials on the Internet, and I will not repeat them one by one here.
3. Import the ACCESS database into sql server2012. The import process is relatively simple, that is, after establishing the database and user name in MS-SQL, click on the database - right button - task - import database.
Special emphasis: It should be noted here that there are 2 items to be checked, otherwise an error will occur
4. Important technical issues: It should be noted here that after the ACCESS database is imported into sql server2012, the auto-increment fields will not be converted, so it needs to be solved manually, and the first field in each imported data table is set to --identity specification -- yes, setting both the self-increment and identityseed values to 1 does the trick. (This step is very important, and most people make mistakes!)
5. Back up the new database. Pay attention to one question when backing up: whether you choose a full backup or a differential backup, this is very important. I suggest that if the amount of data is not very large, use the full backup-option setting to overwrite the current backup, and set a unique path and delete the redundant path, which involves the problem of media sets. Otherwise, there will be multiple incomplete media during the restore, which will be troublesome, and the restore may fail unless you find all the backup sets.