People still need a sense of accomplishment.

From yesterday afternoon till now, I spent a little time finding the problem raised by the local branch and kill the hidden bug in the code, which is very difficult.
Happy and cool!

Solve the strange problem of SQL Server
1. [Microsoft] [odbc SQL Server Driver] timeout has expired
2. Error 5: [SQL-DMO] Code Execution Exception error: prediction_access_violation

Problem Inference

For the first question:
It takes a lot of time to look up the database view. It is inferred that the data volume in the table is too large and the view is composed of three tables. Therefore, the entire join connection, including searching, consumes a lot of time, painful. if you do not want to delete or search SQL statements in the view, this error always occurs. "[Microsoft] [odbc SQL Server Driver] timeout has expired ". in the query analyzer, this view operation also takes about 1 minute 20 seconds to achieve the result. in the same case, it is no problem to open other tables or views. The best way is to clear junk data and recreate the view.

For the second question:
I wanted to increase by 1 MB by setting the database properties, but not only did not grow, but instead came up with a box "error 5: [SQL-DMO]CodeExecution Exception error: exception_access_violation "no better solution, Please reset ur computer.