Viewing 15 posts - 7,231 through 7,245 (of 22,226 total)
SeanNerd (11/14/2014)
"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
November 15, 2014 at 5:13 am
SeanNerd (11/13/2014)
I have a table where we cannot use the typical int identity primary key column. The table can have millions...
"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
November 15, 2014 at 5:11 am
Dana Medley (11/14/2014)
"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
November 14, 2014 at 7:58 am
Yeah, I have to agree. The posted code fails to compile. I can edit it, but I'm guessing I won't see the error if I do.
"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
November 14, 2014 at 6:28 am
Gotta agree. Without an edition being stated, the answers change. Just saying SQL Server, I would assume the full product, then the minimum is 1gb, but the recommended is 4gb....
"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
November 14, 2014 at 4:35 am
You might want to post that on Connect so that Microsoft is aware of it and makes it part of the 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
November 14, 2014 at 4:31 am
Resender (11/14/2014)
We have a similar scenario
A query that runs an inner join on a select statement on a linked server
If the linked server is unavoidable,what...
"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
November 14, 2014 at 4:02 am
If you have the money, you'd better off with more than one disk to stripe the access. Also, for ~600gb of data, 8gb is a shockingly small amount of memory....
"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
November 13, 2014 at 9:11 pm
TheSQLGuru (11/13/2014)
I will add that you must be on Enterprise (or Developer) Edition of SQL Server to use them at all.
Oh, and that. Thanks.
"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
November 13, 2014 at 5:12 pm
OK, that's weird. It just worked the second time? Huh... I'm stumped. That error is pretty explicit. It's not possible that someone has been mucking with the 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
November 13, 2014 at 4:57 pm
GilaMonster (11/13/2014)
g.britton (11/13/2014)
SeanNerd (11/13/2014)
I have a table where we cannot use the typical int identity primary key column. The table can...
"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
November 13, 2014 at 4:29 pm
A little confused by what's going on. Red Gate (good choice) SQL Compare doesn't do backups and restores. It just compares databases to other databases, backups, scripts, source control, 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
November 13, 2014 at 3:51 pm
Just make sure you carefully document what you're removing and have it stored somewhere that everyone remembers.
"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
November 13, 2014 at 3:43 pm
Based on the fact that you're seeing performance increase after FREE_PROCCACHE, while it may be other things, it's more than likely first and foremost, bad parameter sniffing. You need 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
November 13, 2014 at 3:41 pm
Then that's odd. I can't recreate it. Here's what I did. I opened a session and used this code:
CREATE PROCEDURE dbo.TestingColumns
(@SalesOrderID INT)
AS
SELECT soh.SalesOrderID
FROM Sales.SalesOrderHeader AS soh
WHERE soh.SalesOrderID = @SalesOrderID;
Then...
"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
November 13, 2014 at 8:10 am
Viewing 15 posts - 7,231 through 7,245 (of 22,226 total)