New answers tagged

3

A deadlock is a kind of serialization error: you didn't do anything forbidden, it just so happened that there was an interaction with other active transactions that prevented your transaction from being completed. Your reaction is the correct one: retry the transaction. There is absolutely no need to wait before retrying. I concur that with a sufficiently ...


0

Error 18456; Severity 14; State 38 Failed to open the database specified in the login properties. (or) Cannot open database "" requested by the login. The login failed. State 38: Could not find database requested by user. Run the following command and check the result: SELECT * from sys.databases Depending on the results, we can identify how we ...


2

I'm assuming you're talking about ad hoc SELECT queries, not views or reports. Views and reports (the queries underlying reports) are best verified by a controlled test suite. A controlled test suite would also verify SQL UPDATE and DELETE queries. If the situation is complex, you might have to build a test suite for an ad hoc query. Having said all that, ...


3

Unfortunately your question is too generalized and broad to be answerable on here. It's going to be situational and depend on what you're trying to query for. It's no different than checking anything else, such as if your application code is working correctly. You'll need to analyze the outputted result, and see if it makes sense for what you're trying to ...


Top 50 recent answers are included