Viewing 15 posts - 676 through 690 (of 789 total)
Personally I'd track any DML that's not within an SP. Starting with TSQL:SQL:StmtStarting and then filtering out obvious garbage (SET statements etc). That may come close, but then...
June 30, 2003 at 9:26 pm
Often my first action in such circumstances is to run profiler interactively (locally if possible) to capture SQL with a CPU > zero. I tend to run it for...
June 30, 2003 at 5:08 pm
Were they valid login names on your server? ie. I seen servers open to the Internet that regularly experience similar hack attempts on login ids such as SA, SQL,...
June 30, 2003 at 4:46 pm
Change to the schema affect the system tables which, unfortunately, cannot have triggers on them.
You can schedule a 24-hour trace on the server, looking for statements starting with CREATE, DROP...
June 30, 2003 at 4:35 pm
If you used the SQL Server Agent thingy in BackupExec then you may not be given the option of doing as Shas3 suggests. If that's the case, and if...
June 29, 2003 at 11:54 pm
Those busy objects are MYSQL components (data, log and error files).
Looks like you're trying to back up MYSQL database files whilst the Mysql service is still running.
June 29, 2003 at 11:44 pm
There could be so many locks taken that locks are escalated to page or even table locks. You may want to run Profiler and look at lock acquisition and...
June 29, 2003 at 11:33 pm
Is "Compilations/Sec" different to "re-Compilations/Sec"? The latter may refer to SPs whilst the former to any ad hoc SQL batches?
June 29, 2003 at 11:27 pm
Hmmm. Quite complicated, especially with VAR*, N*, text and nullable columns. Also the setting of text-in-row for the table would probably have an effect.
Suggest having a...
June 29, 2003 at 6:52 pm
You've hit the SQL 6.5 hard limit of 64k bytes in a stored procedure. (this limit became about 250mb with the introduction of SQL 7.0). This is 255...
June 29, 2003 at 4:27 pm
I don't have your schema, so here's a NORTHWIND example of using sp_executesql with:
- a dynamically constructed SQL string (equivalent to tacking @psyntax on the end)
- an input parameter...
June 26, 2003 at 4:21 pm
It MIGHT be an ambiguity arising from your outer join syntax. Possibly worth trying a LEFT OUTER JOIN instead of "*=". From BOL:
June 26, 2003 at 3:37 pm
Sorry, but I can't go back to SP2 either. I guess the next step would be for you to send a query to the xpsmtp people.
June 26, 2003 at 1:46 am
Viewing 15 posts - 676 through 690 (of 789 total)