Viewing 15 posts - 20,761 through 20,775 (of 22,219 total)
Not for me. In general, the suggestions so far won't hurt performance on a 2gb database and they will help performance on larger databases. It's easy and free, so why...
"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
April 1, 2008 at 10:01 am
Bad news, that must have been someone's private example. I don't have anything like that in the slides that they provided to us. I wish I did. The slides provided...
"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
April 1, 2008 at 9:59 am
And to really muck up the environment some more, add a filegroup for storing text or (MAX) columns too.
"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
April 1, 2008 at 9:36 am
One other note, we do this regularly because, as Steve state, sharing the load across multiple access points is a simple win. However, you now need to be careful about...
"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
April 1, 2008 at 9:23 am
Yeah, that's true. Sorry, I should have clarified. My issue is to prevent the INSERT...SELECT...INSERT chain and the OUTPUT clause bypasses that horror show quite well. I do tend to...
"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
March 28, 2008 at 9:45 am
Here's a quick example. I'm only using a single row, but the same methodology will work with multiple rows:
CREATE TABLE Master1
(
Master1Id...
"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
March 28, 2008 at 8:49 am
Jack Corbett (3/28/2008)
"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
March 28, 2008 at 8:03 am
Yeah, Microsoft Connect. You can submit requests for features or changes, etc. Then, you can let others know about the change you've submitted and they can go & vote 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
March 28, 2008 at 7:04 am
Honestly, neither.
What scares me is medical data. I was working for a software start-up that provided software to doctors. Not only did it store full patient history, but it had...
"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
March 28, 2008 at 6:48 am
We did tests in the past and found that for simple lists, UDF's were WAY better than XML. XML started to shine when we were working with more complex structures.
BTW,...
"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
March 28, 2008 at 6:44 am
You can use the SQL Server Management Studio to connect to and work with Compact databases though, if that helps. It's not stored procedures but it is a bit easier...
"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
March 28, 2008 at 6:10 am
Version 8.0 is actually "SQL Server 2000."
It sounds like security has changed inside your database? Possibly.
"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
March 27, 2008 at 12:50 pm
What error? Are you running in SQL Server 2008? This is a 2008 forum.
"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
March 27, 2008 at 12:40 pm
Looks like tempdb ran out of space.
Either you ran a query against such a large amount of data that you maxed out your tempdb or you may have something wrong...
"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
March 27, 2008 at 12:28 pm
Also it could be the statistics are changing in your data. Make sure that they're up to date. It's really important, as noted above, to look at the execution plan,...
"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
March 27, 2008 at 11:46 am
Viewing 15 posts - 20,761 through 20,775 (of 22,219 total)