Notes for release systems

1: Problem: After the system is released, you can find some Chinese characters in the report are garbled. You can only find out that these Chinese characters are returned from the stored procedure. Why is there no such problem in the development environment? Finally, the cause of the problem is clear. In the past, the database servers actually deployed were in English and the database servers in the development environment were in Chinese. The varcha type in the stored procedure does not support Chinese encoding in the English operating system, chinese encoding is supported in the Chinese operating system.
Solution: Change the varchar type in the stored procedure to nvarchar (UTF-8 encoding supported ).

2: After the system is released, the data displayed in a data list is incorrect. The data list extracts data from a view. Why? It turns out that a source table in this view changes the table structure and deletes a column, but the view does not automatically update and remove the column.
Solution: Open the view designer, run the view, and manually update the view (the view is not automatically updated ). It is recommended that you do not useSelect *And useSelect Field 1, Field 2 .......

3: problem: a function is abnormal after the system is released. After checking, it is found that this function applies a stored procedure, the stored procedure failed because it exceeds the permissions of the database users who are currently deploying the system! The SA Super User is used for testing in the development environment. Of course, this cannot be checked.
Solution: Modify the stored procedure. During the test, try to make the test environment consistent with the deployment environment.