Viewing 15 posts - 13,981 through 13,995 (of 22,219 total)
GilaMonster (10/30/2010)
Grant Fritchey (10/30/2010)
The default trace does not store data manipulation calls. In order to track those you'll have to create your own server side trace.
Or put triggers on the...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
October 30, 2010 at 11:44 am
The default trace does not store data manipulation calls. In order to track those you'll have to create your own server side trace.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
October 30, 2010 at 10:21 am
The more important question to ask is, why is your log growing? Do you have a database in Full Recovery mode, but you're not running backups? Do you have log...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
October 30, 2010 at 10:14 am
This is the Microsoft documentation. What are you looking for?
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
October 30, 2010 at 10:12 am
Since the statistics are stored with the database (except in the case of an upgrade, as was mentioned), they will be moved with that database. This means, if the statistics...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
October 30, 2010 at 10:07 am
Then you'd probably be better off doing the integration some other way, call both databases from the app instead of one database from the other database, something along those lines.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
October 29, 2010 at 7:46 am
GSquared (10/29/2010)
That seems to be what you're describing.
If so, that's probably a major part of...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
October 29, 2010 at 7:40 am
parthi-1705 (10/29/2010)
Grant Fritchey (10/29/2010)
You're really naming all your columns, Col1, col2... Troubleshooting and developing against that should be a lot of fun.
The Column name i have kept on my server...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
October 29, 2010 at 7:32 am
Back to the original purpose of this thread, my only response to this, once the clarification was in, is WTF?!?
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
October 29, 2010 at 7:29 am
SELECT * FROM Table
This query will simply scan the table. So, performance is strictly up to the hardware. How fast are your disks? How fast is your CPU? That's...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
October 29, 2010 at 7:23 am
There just isn't any magic way to kill a process. If you know where the problem is, I'd concentrate on fixing it. If a transaction is opened and running, when...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
October 29, 2010 at 7:07 am
For no cost, you can install PowerShell and put that to work, again using SMO. A script to generate all database objects would only be about 30 lines. I have...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
October 29, 2010 at 7:05 am
You're really naming all your columns, Col1, col2... Troubleshooting and developing against that should be a lot of fun.
What kind of query are you trying to run? You don't list...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
October 29, 2010 at 6:59 am
Yep, Marco has nailed it. A trace runs on an instance. You can filter the trace.
I'm a bit confused over what you're trying to do. You talk about all databases...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
October 29, 2010 at 6:56 am
Can you please show what you've tried that hasn't worked. We're more than willing to help. But, we're not doing your homework for you.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
October 29, 2010 at 6:53 am
Viewing 15 posts - 13,981 through 13,995 (of 22,219 total)