SQLSaturday SLC 2010

Comments: No Comments
Published on: September 1, 2010

Well, I have taken another plunge.  I finally got around to submitting a session for SQL Saturday Salt Lake City 2010 (Web | #sqlsat54 ).  I had been planning on doing this since it was announced through the grapevine.  The delay for submitting the first session really came down to a bit of confidence in writing an abstract on the topic.  Writing abstracts is new territory for me.  I plan on improving in this domain, thus will need to submit a few more abstracts to various different events.  That said – SQL Sat SLC will be the first but not the last.  If you check out the website for SQL Saturday 54, you will see that my topic is one of those that brings agony to many DBA’s – Documentation.  As I said in the abstract, I hope to share some scripts to help simplify some of the documentation tasks.

I am looking forward to this event and hope to see some of you there.  Here’s to hoping my presentation will be selected.  In the meantime, I will be working on another abstract for a second topic to present at SQLSat54.

No Comments - Leave a comment

Leave a comment

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code class="" title="" data-url=""> <del datetime=""> <em> <i> <q cite=""> <strike> <strong> <pre class="" title="" data-url=""> <span class="" title="" data-url="">

September 2010
« Aug   Oct »


  • @tradney: @zahirmohideen There will always be some SQL files on C:,you can't change, however you can specify a diff drive for most else. #sqlhelp
  • @zahirmohideen: How to avoid any install files ( including essential ) in c: drive ( system drive) ? . I am installing sql binary in other drive #sqlhelp
  • @DBArgenis: @EnlightenData I would never try to schedule those two at the same time, though. Bad idea in general. #sqlhelp
  • @DBArgenis: @EnlightenData incorrect. Backups don't take table locks. #sqlhelp
  • @EnlightenData: I assume an index REBUILD would block a FULL database backup from continuing due to a table lock. Correct? #sqlhelp
  • @meyer_tom: seems that an Alert for message 1480 will only fire if set to <all databases> and not just one. Expected behavior ? If so, why ? #sqlhelp
  • @Dan_Doucet: #sqlhelp wondering if removing a column from an existing non clustered index requires downtime? Table would have about 6million rows
  • @SQLSoldier: @EnlightenData Long running transactions keeping really old versions in tempdb. #sqlhelp
  • @SQLSoldier: @EnlightenData Sufficient space for versioning in tempdb. Very wide rows that don't have room for the version pointer (14 b). #sqlhelp
  • @Chris_Kasten: Details: users are running an old .NET app from their workstations. App hasn't changed in years. No maint on the server in weeks #sqlhelp

Welcome , today is Thursday, January 29, 2015