Viewing 15 posts - 13,126 through 13,140 (of 49,552 total)
Stefan Krzywicki (5/17/2013)
Lynn Pettis (5/17/2013)
Lynn Pettis (5/17/2013)
After the date was changed to 2032 , scheduled jobs did run no issues. After changing the date to 2013...
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
May 17, 2013 at 11:45 am
And the trigger definition looks like....
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
May 17, 2013 at 11:41 am
btw, the WAITFOR is not necessary to get that lock. USE ADVENTUREWORKS is sufficient.
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
May 17, 2013 at 11:38 am
Please post new questions in a new thread and give as much information as possible, including errors and the output of CheckDB.
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
May 17, 2013 at 11:37 am
That's a shared database lock. Each and every running query, no matter what it's running, takes a shared database lock to ensure that the database can't be dropped while 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
May 17, 2013 at 11:32 am
Grant Fritchey (5/17/2013)
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
May 17, 2013 at 11:29 am
Lynn Pettis (5/17/2013)
Is that from the same person who thinks that NOLOCK makes queries run faster?
Which one of them?
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
May 17, 2013 at 9:27 am
T.Ashish (5/17/2013)
So should I say that it is the old way of INNER JOINing tables, that will not be supported in future versions !!
It's the old way, but it's not...
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
May 17, 2013 at 9:24 am
Delete data, add more space or move stuff to another drive.
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
May 17, 2013 at 9:09 am
As I said, MAXDOP is just the maximum number of processors and MAXDOP 0 means use up to the total number of processors, but it's up to the optimiser and...
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
May 17, 2013 at 8:23 am
T.Ashish (5/17/2013)
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
May 17, 2013 at 8:22 am
Maxdop is just that, Maximum degree of parallelism, the maximum number of cores that the query can use. A query with MAXDOP 8 can run on a single core if...
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
May 17, 2013 at 7:57 am
"I know the drawbacks of nolock, in our case it cannot be avoided"
Hmm...
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
May 17, 2013 at 7:24 am
T.Ashish (5/17/2013)
Though I know the drawbacks of NOLOCK, it can't be avoided in our case.
Really? So you absolutely must allow potentially incorrect data in results because ....
And regarding...
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
May 17, 2013 at 7:22 am
marc.snoeys (5/17/2013)
But, my personal opinion is that it would be more intuitive to be able to write an INSERT-statement just like an UPDATE-statement.
Personally I'd prefer an update in the form...
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
May 17, 2013 at 7:02 am
Viewing 15 posts - 13,126 through 13,140 (of 49,552 total)