Viewing 15 posts - 15,931 through 15,945 (of 49,552 total)
You either haven't enabled AWE, haven't granted locked pages permission or haven't put the /PAE switch in boot.ini (or more than one of those). When you've got AWE working, SQL...
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
October 25, 2012 at 3:21 am
Give the user select rights on the tables and execute rights on the procedures. It will work exactly as you want. They'll be able to only select directly from the...
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
October 25, 2012 at 3:17 am
The X and U locks are key locks, not object locks. Each one is locking a different row in the index.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
October 25, 2012 at 3:14 am
You have 32 bit SQL and are not using AWE.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
October 25, 2012 at 3:11 am
Target = total, stable memory allocation
Target > total, SQL's still allocating memory and building up the caches.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
October 25, 2012 at 1:46 am
It's a combination of this http://sqlinthewild.co.za/index.php/2008/02/25/parameter-sniffing-pt-2/ and the fact that the index is not covering
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
October 25, 2012 at 1:45 am
peterdru401 (10/24/2012)
check which query is lock the object u r trying to truncate by following.Select blocking_session, sid, serial#, wait_class,seconds_in_wait From v$session where blocking_session is not NULL order by seconds_in_wait
Is v$session...
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
October 25, 2012 at 1:40 am
Something's blocking the truncate.
Check sys.dm_exec_requests, see what the wait type is, what the blocking session is. See what that blocking session is/was doing.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
October 25, 2012 at 1:39 am
JimRush (10/24/2012)
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
October 25, 2012 at 1:35 am
If SQL has allocated 94 GB then it is using 94GB. If that's too much, reduce the max server memory setting.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
October 25, 2012 at 1:32 am
Try 10 000 000 and 100 000. Don't test on small numbers of rows, the results will be lost in the measuring error.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
October 24, 2012 at 3:09 pm
Test and see?
I would guess pretty much comparable.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
October 24, 2012 at 2:36 pm
It is not just that. Check and ensure that it is certified for SQL Server, that it supports SQL Server. EMC should have that explicitly stated somewhere in their docs,...
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
October 24, 2012 at 2:24 pm
A char(2) takes 2 bytes, a varchar(2) takes 2-4 bytes, A char(3) takes 3 bytes, a varchar(3) takes 2-5 bytes, etc. I'll usually switch around 4-6 characters, unless the column...
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
October 24, 2012 at 1:21 pm
Yup, I've seen similar.
Most likely cause, your SAN replication is not following the rules that SQL needs out of an IO subsystem (write order preservation mainly). Check that the...
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
October 24, 2012 at 1:17 pm
Viewing 15 posts - 15,931 through 15,945 (of 49,552 total)