Viewing 15 posts - 23,041 through 23,055 (of 49,552 total)
jared-709193 (10/5/2011)
Umm... Why not? 🙂
Because it's not really necessary on a dedicated SQL box. I usually create one of a couple GB, no more. Just enough for a kernel dump...
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 5, 2011 at 2:38 pm
Something interesting I noticed about the Rugby WC quarter finals.
On Saturday Ireland is playing Wales and England playing France
On Sunday SA plays Australia and New Zealand plays Argentina.
In the semis,...
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 5, 2011 at 2:34 pm
SQLRNNR (10/5/2011)
How are things going for the All Blacks and SpringBok?
Springboks (one word, one capital), winners of Group D, playing Australia (ouch) on Sunday.
All Blacks, winners of Group A,...
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 5, 2011 at 2:30 pm
JimS-Indy (10/4/2011)
I'll set a default to avoid null.
If the column mustn't be null, define the column as NOT NULL, otherwise default or no default, nulls can go in.
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 5, 2011 at 12:20 pm
Have you tried traceflag 1222? If so, what doesn't it give you in terms of information?
Jonathan's right, a memory dump (even a mini-dump) isn't what I'd call a low-impact event.
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 5, 2011 at 11:59 am
You get a difference because the query adds the milliseconds since the computer started to the time that SQL started. So if SQL Server started 27 seconds after the computer...
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 5, 2011 at 10:57 am
Why a memory dump? That seems to be a very inefficient alternative to the usual traceflags, profiler events or extended events for diagnosing deadlocks.
p.s. I apologise for the brief answer,...
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 5, 2011 at 10:09 am
I'm not sure what the problem is here. Filestream data is backed up with the database, that's one of the key advantages of it over regular files in the filesystem.
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 5, 2011 at 10:06 am
Yes and yes. Restoring a database clears the plan cache.
p.s. It's called the plan cache, not the procedure cache because it caches a lot more than just stored procedures.
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 5, 2011 at 9:35 am
The plan cache is shared between all databases, but procedures in different databases are considered different objects and will have separate plans.
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 5, 2011 at 9:14 am
You can't see the row because you're not inserting the ID columns hence there's no way the new rows will join to each other. Since they don't join, they won't...
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 5, 2011 at 8:57 am
99zardoz (10/5/2011)
Do you like your database consistent and durable or corrupt with missing data? If the latter, sure, they're of little practical use. The point of the log is to...
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 5, 2011 at 8:29 am
And maybe also monitor compiles
http://sqlinthewild.co.za/index.php/2010/07/27/hit-and-miss/
http://sqlinthewild.co.za/index.php/2010/08/31/come-and-gone/
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 5, 2011 at 7:44 am
Since you shrunk the database, you now need to rebuild all your indexes to fix the fragmentation.
As for the log, these may be useful.
Managing Transaction Logs[/url]
http://www.sqlservercentral.com/articles/Transaction+Log/72488/
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 5, 2011 at 7:35 am
http://sqlinthewild.co.za/index.php/2007/11/15/execution-plan-operations-scans-and-seeks/
http://www.sqlservercentral.com/articles/Indexing/68439/
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 5, 2011 at 7:34 am
Viewing 15 posts - 23,041 through 23,055 (of 49,552 total)