Hot answers tagged debugging
4
I was able to solve the problem by thinking about the error message for a minute. The error message says something about not being able to convert from varchar to int. So I looked for columns that should store a number, but were actually saving it as a varchar. The necessity of a cast was an indicator.
So, I looked through each column in the ...
4
"Sometimes this deadlocks - two threads with different queries never ends"
What you are experiencing is blocking, not deadlock. When a deadlock condition occurs, SQL server automatically detects it and choose one of the queries as a victim and throws error 1205.
If you are really experiencing deadlock errors, turn on trace flag 1222. It will log the ...
3
I don't know anything about Remote Debugging, but you can use Windows Authentication between two computers on different domains or with no domain, if they have an identical user account with the same password.
On the client machine, create a Windows account UserSQL, with password test123
On the server, create a windows account UserSQL, with password ...
3
While I'm not sure if it's the easiest way, you can use an "after servererror on database" trigger to log all errors to a table.
See http://nadvi.blogspot.se/2010/12/log-all-database-errors-to-table.html
See also http://psoug.org/reference/system_trigger.html
The documentation for system event triggers is here: ...
2
Your SSIS package would be stored as a .dtsx file, or perhaps in the MSDB database. Either way, you should be able to locate it, open it in a copy of BIDS that you run as the user that executes the application, configure BIDS to have the same set of conditions as how you call the package, and then debug it from there.
2
You can find some good information regarding security from the article below.
Reviewing SQL Server Permissions | TechRepublic http://tek.io/KfzEyp
Except:
The following query uses the sys.database_permissions system view to
indicate which users had specific permissions inside the current
database.
SELECT
dp.class_desc
...
1
You should be able to see them with SQL Profiler.
See this link
http://msdn.microsoft.com/en-us/library/ms178104(v=sql.105).aspx
Also, if you suspect a query causes your deadlock, you can try to add the "WITH NO LOCK" clause. But it should not be a permanent solution.
Ultimately, you should take the different queries and see why they cause a lock. Maybe ...
1
You can have a high load from lots of short queries as well. Try setting your long_query_time to 0, and force all clients to reconnect. Let that run for a few minutes and then set it back to your default. You can peruse the results by hand or use a tool like pt-query-digest.
In either case, you should be able to figure out if there is in fact a bunch ...
1
I do not think for v5.0.95 is it possible to enable general log without server restart, but
as of MySQL 5.1.12, you can by executing this query,
You can try this on v5.0.95 as well and see whether it works or not,
SET GLOBAL general_log = 'ON';
This method works on any platform and does not require a server restart.
Baron has written a script to ...
1
I'm not sure how helpful this answer is for you, but another option is to open Visual Studio rather than SQL Management Studio, and open the View->'Server Explorer' option. Add a new connection to the database in question, then drill through to the stored procedure of interest, then right click and select 'Step-Into Stored Procedure', which will prompt you ...
1
That bug is referenced in the MySQL Documentation for 5.5 and 5.1.40+ as that condition being unsafe.
Note the bottom of the bug report:
[10 Dec 2010 3:34] Daogang Qu Any statement that causes a trigger or
function to update an AUTO_INCREMENT column is considered unsafe for
statement-based replication after a patch of
...
Only top voted, non community-wiki answers of a minimum length are eligible
