This book was infected. After successfully killing it with anti-virus software, it still restarted inexplicably. There were many errors at startup, so I reinstalled it.
As a result, it was installed three times in 24 hours. Do you know why? After installing the system, install Microsoft Virtual Machine 2004, and Windows Server 2003 Enterprise Edition will start and run miraculously. sweat. So after going through it twice, I finally found out that the problem was with the virtual machine, so I decided not to install the virtual machine angrily, and also deleted the virtual machine hard disk virtual files that I specially kept. No need...
Later, after I googled it after my notebook was fixed, I found out that the virtual machine might be in conflict with a patch from 2003. possible? Let’s forget about it…
Having said so much, let’s get to the point.
After installing Sql Server 2005 Developer, hit Sp1. Everything has just been installed, and there is only the default database in the database.
But Sp1 prompts an error! There were many, many errors, and finally it was prompted to restart. I started it, and after opening it, I found that Sp1 was still not enabled. The version number is still the RTM version number that excited me before. This certainly didn't work out.
So again, it’s still wrong.
What's the problem? After reading the English installation instructions N times, I have done everything I need to do, and it has just been installed, so there should be no errors.
It turns out that there was also a problem when installing Sp1 in the virtual machine. I wasn't in the mood at that time so I didn't care.
Finally, I looked at the English installation instructions. Still to no avail.
sweat! The weather here in Shanghai is changing so fast. It just rained for a day, and now it's getting hot all of a sudden.
In a fit of anger, I shut down all services of Sql Server. Start the game.
After the game, I still felt unhappy looking at Sp1 on the desktop. Come again. Passed?
Looking at a pile of success! Speechless!
So I took another look at the English installation instructions. I need to close all Services and Applications before installation. It seems that there is something wrong with my English understanding! The most important Sql Server 2005 service is not closed, but analysis, reporting and other services are closed! I understood it as the services and applications related to it, but did not consider it itself.
Everything is fine, happy.
But...
Tonight, I will help my friend with a graduation project. Suddenly it occurred to me that the database design structure of the website that was half-finished last time was the same as this one. It was not done last time.
Open Sql Server Management Studio and execute attach!
It seemed that I had no choice but to cry. I reinstalled the system three times in 24 hours. Also...
It seems that I need to restore the backup. Fortunately, I was prepared in advance.
Keep making mistakes...
cry! I said to myself.
This database is almost finished, so we can’t do this. I made the same mistake last time after deleting the database and redoing it. However, the database last time only had a few simple tables and nothing else. The tables in this one are all secondary, including storage procedures, data... I dare not Think about it.
So I looked at the English prompts in a daze.
The last time the attach error occurred after the system crashed. I thought it was caused by not shutting down Sql Server strictly midway. But now that I think about it, sometimes I suddenly restart my computer and do a cold restart. But there is no problem after restarting.
It seems that there is no problem with reinstalling the system.
It seems that my last strict detach was not necessary before reinstalling the system. But there’s nothing wrong with getting used to it. But now I’m sure it has nothing to do with that.
So I tried it again, looked in English, and said the system could not be accessed. Suddenly I thought about the security properties of files.
Finally, I found it and stopped crying.
It turns out that there is only one garbled user in the security attributes of these two database files, and there are no other users, which means that the local administrator does not have permission to use them. Especially for things like Sql Server that pay attention to security, they pay more attention to this. Add users to it.
Everything is fine.
attach successfully!
To sum it up!
When installing Sql Server 2005 Sp1, you need to close all Sql Server services and related applications.
Before attaching, make sure that the current system has permissions for the database files used.
PS: I actually didn’t shed a single tear, all the crying above was just literary exaggeration!