Viewing 15 posts - 18,811 through 18,825 (of 22,219 total)
AndyD (1/9/2009)
"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, 2009 at 5:48 am
I've climbed under desks and pulled cable in a suit and tie and I've worked in shorts & sandals at a dot com. In neither situation was I more or...
"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, 2009 at 5:43 am
Here in New England... it's a New England winter only a little more so. We could use a bit of global warming. There's about 3 inches of completely frozen snow...
"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, 2009 at 5:33 am
GSquared (1/8/2009)
Grant Fritchey (1/6/2009)
GilaMonster (1/6/2009)
Grant Fritchey (1/6/2009)
I must be old, D&D used lots (and lots and lots) of six-sided dice. Now, Traveller, there were the decimal dice at work.
Which edition...
"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, 2009 at 5:31 am
Also, is this a transactional system or a BI system? 60 columns for some of the BI systems I've seen is pretty standard.
"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, 2009 at 12:41 pm
Vijaya Kadiyala (1/8/2009)
SQL Server performs a join between two sets of row data using the merge
join algorithm. The inputs are two separate sets of row data. Output...
"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, 2009 at 11:39 am
Something I hadn't thought of earlier, but you might check the ANSI settings on the connection string from Access. If you use the ANSI standard settings, performance should be fine,...
"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, 2009 at 9:31 am
Ah, then it's not going to be solved by tweaking indexes and messing with the execution plan. Something is going on in the network or with the Access app.
"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, 2009 at 9:13 am
I don't see 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
January 8, 2009 at 8:50 am
jonathan allen (1/8/2009)
OrgName
FROM Organisation
ORDER BY OrgName
Clustered Index Scan on Primary Key - 95%
Sort (on Indexed OrgName...
"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, 2009 at 8:40 am
The execution plan is your friend.
That will tell you what's occurring within the query.
"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, 2009 at 8:28 am
I would put the customer information in a common table. 40 customers = 40 tables, with 40 different queries and 40 different indexes and 40 different maintenance plans... Oh, and...
"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, 2009 at 7:32 am
Well, there are no guarantees, but I'd say, it depends on what your script is doing. Your standard, every day, every second, script that's updating a set of tables... it...
"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, 2009 at 6:04 am
I agree with Peso.
Think about it. First, you'd need 365 seperate tables for just one year worth of data. Second, your queries would have to be changed, every single day,...
"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, 2009 at 6:01 am
I've got SQL Server 2000, 2005 and 2008 running on one machine along with three different copies of Express. All with no issues.
My understanding is that you can install Management...
"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, 2009 at 5:47 am
Viewing 15 posts - 18,811 through 18,825 (of 22,219 total)