Viewing 15 posts - 10,201 through 10,215 (of 22,224 total)
Filestream would be the preferred method if you have to store things within the database. You can store them in a varbinary(max) column, but you have to deal with special...
"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
January 9, 2013 at 4:37 am
hisakimatama (1/8/2013)
"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
January 8, 2013 at 12:52 pm
They want ALL that and only want to pay $55k? I'd tell 'em where to shove that. That's crazy.
"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
January 8, 2013 at 12:39 pm
Yeah, not sure. That syntax looks a little odd. It's not a sqlcommand parameter. It' not a normal parameter. Best thing would be to go back and reread whatever documentation...
"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
January 7, 2013 at 4:52 am
Sounds like whatever transaction was running stopped and the tempdb emptied back out. Normal, if unfortunate, behavior. I'd try to track down where that query came from because, if your...
"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
January 7, 2013 at 4:48 am
Differentials only capture data changes since the last full backup. And, differentials won't help you with the logs. The best answer is to follow Gail's advice and run more frequent...
"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
January 7, 2013 at 4:46 am
I don't suppose you still have the original question? Anyone else searching for similar help can benefit from the question and answer. Editing it away makes it more difficult 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
January 7, 2013 at 4:44 am
I'm with Joe and Dwain.
You do have an option, but it's somewhat dangerous. SQL Server has a function called SOUNDEX that sounds out how a word would be spoken. This...
"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
January 7, 2013 at 4:43 am
There's almost no difference between the two. Both are likely to cause HUGE issues. Updating that much data using a cursor AND through individual INSERT & UPDATE statements is going...
"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
January 7, 2013 at 4:38 am
When looking at the wait stats, order them by the total wait time and you can see what is causing things to slow down. This is a simple version 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
January 6, 2013 at 4:06 am
Like I said, sys.dm_exec_requests combined with the locking and transaction dynamic management objects.
"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
January 4, 2013 at 11:55 am
After the fact it's going to be hard to track down. You can try using sys.dm_exec_query_stats to see which queries have the most worker_time. That will give you some indications...
"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
January 4, 2013 at 10:34 am
stuart.holloway (1/4/2013)
To resolve the issue, it was quicker...
"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
January 4, 2013 at 6:09 am
anthony.green (1/4/2013)
2 - Yes as long...
"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
January 4, 2013 at 4:19 am
Resender (1/4/2013)
1)A user has select rights to tables...
"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
January 4, 2013 at 4:18 am
Viewing 15 posts - 10,201 through 10,215 (of 22,224 total)