Viewing 15 posts - 21,631 through 21,645 (of 22,224 total)
Tami D (10/23/2007)
"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 24, 2007 at 6:31 am
Even though I didn't have all the information, despite the number of rows, it's not a very big table. I did some experimentation. They shouldn't be hitting any issues assuming...
"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 24, 2007 at 6:18 am
webrunner (10/23/2007)
Jereme Guenther (10/19/2007)
I obtained a BS in Software Engineering picking...
"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 24, 2007 at 5:23 am
I set up a sample using these scripts:
CREATE TABLE BigTable
(
ID INT,
Date SMALLDATETIME,
[Value] decimal(18,10)
)
WITH x AS (SELECT 1000001 AS Id
,GETDATE() AS MyDate
,42.2 AS MyValue
UNION ALL
SELECT
ID + 1
,MyDate
,MyValue
FROM X
WHERE ID <...
"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 23, 2007 at 10:35 am
I've never heard of anything like that. Best guess I can come up with (and it stinks) is to run spell check on the fields after you concatenate them...
"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 23, 2007 at 10:30 am
That's good.
On which columns? Is it the PK? If not the PK, is it unique? What does the query plan that is taking 3 minutes look like and how...
"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 23, 2007 at 9:01 am
All three of the Inside SQL Server 2005 books provide information you'll need.
"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 23, 2007 at 8:55 am
Ignore my last post. It's utterly 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
October 23, 2007 at 8:54 am
What kind of indexes do you have on the table?
"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 23, 2007 at 6:55 am
It is a security issue. You have to make that determination for yourself. It's off by default. Run sp_configure. It's the setting 'Remote Proc Trans' and setting it to 1...
"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 23, 2007 at 6:47 am
What problems specifically are you worried about or experiencing?
54 million rows that are composed of one integer column just isn't going to be an issue. Are you experiecing fragementation 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 23, 2007 at 6:40 am
The issue you're running into is the logical processing order. The SELECT list is processed after the FROM, ON, JOIN, WHERE, GROUP BY, WITH, HAVING clauses. Any reference to items...
"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 22, 2007 at 11:36 am
The variant doesn't scare me (much), but everything into one table? How many users are expected to access this? What does the indexing look like? Has anyone vetted the design...
"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 22, 2007 at 9:21 am
Yeah, I mean, we had every single possible good technical, security and performance reason not to give them what they asked for. However, they trumped all those with a phone...
"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 22, 2007 at 7:03 am
You're trying to combine the function of EXEC where it executes an ad hoc sql string with the function of exec where it captures the return status of the execution...
"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 22, 2007 at 6:59 am
Viewing 15 posts - 21,631 through 21,645 (of 22,224 total)