When doing database experiments, I encountered a little "little trouble". As shown below:
I create a trigger, execute it, and it throws an error.
It says to turn on the error log, fix the errors, and restart the database.
The error log is under SQL Server Agent, double-click the file under the error log to view it.
After looking at it, there are quite a lot of problems, and then I am learning and modifying it. However, it is useless, and it still reports an error when it should be reported.
Since it is useless to modify according to the error log, it can only be done hard!
Restoring the database, discussing the importance of database recovery technology (just like we need to save the game in time), of course, is useless. So is the detached database.
Tried many times without success.
Finally, I took a break, and when I came back, "Individual User" was displayed at the back of the database , and then I couldn't do anything. Then refresh it, the database is gone, and then I can import it and use it normally.
I reflected on it, maybe it reported an error, but some powerful operations can still take effect. It just might freeze for a while. The IT industry is also one that requires care and patience.
Finally, I wish all elementary school students who have graduated from elementary school for more than ten years and decades, Happy Children's Day!
Your likes, favorites and attention are the greatest support for me.