<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://sqlblogcasts.com/utility/FeedStylesheets/atom.xsl" media="screen"?><feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en"><title type="html">Grumpy Old DBA -  Beware the darkside !</title><subtitle type="html">The Grumpy Old DBA is an independent DBA. Specialising in production support,  performance, tuning and optimisation of SQL Server databases and applications. </subtitle><id>http://sqlblogcasts.com/blogs/grumpyolddba/atom.aspx</id><link rel="alternate" type="text/html" href="http://sqlblogcasts.com/blogs/grumpyolddba/default.aspx" /><link rel="self" type="application/atom+xml" href="http://sqlblogcasts.com/blogs/grumpyolddba/atom.aspx" /><generator uri="http://communityserver.org" version="3.1.20917.1142">Community Server</generator><updated>2011-11-21T20:12:00Z</updated><entry><title>Not obvious then ?</title><link rel="alternate" type="text/html" href="http://sqlblogcasts.com/blogs/grumpyolddba/archive/2013/01/10/not-obvious-then.aspx" /><id>http://sqlblogcasts.com/blogs/grumpyolddba/archive/2013/01/10/not-obvious-then.aspx</id><published>2013-01-10T12:49:00Z</published><updated>2013-01-10T12:49:00Z</updated><content type="html">I requested that we service pack a third party app - here&amp;#39;s the response I have received a reply back from Engineering that SP4 is certified now with WLE 7.x. Engineering ran some tests against SP4 and it runs fine and doesn&amp;#39;t introduce any obvious problems....(&lt;a href="http://sqlblogcasts.com/blogs/grumpyolddba/archive/2013/01/10/not-obvious-then.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://sqlblogcasts.com/aggbug.aspx?PostID=16409" width="1" height="1"&gt;</content><author><name>GrumpyOldDBA</name><uri>http://sqlblogcasts.com/members/GrumpyOldDBA.aspx</uri></author><category term="File Under Grumpy" scheme="http://sqlblogcasts.com/blogs/grumpyolddba/archive/tags/File+Under+Grumpy/default.aspx" /></entry><entry><title>You couldn't write it - Expired SA account</title><link rel="alternate" type="text/html" href="http://sqlblogcasts.com/blogs/grumpyolddba/archive/2012/11/11/you-couldn-t-write-it-expired-sa-account.aspx" /><id>http://sqlblogcasts.com/blogs/grumpyolddba/archive/2012/11/11/you-couldn-t-write-it-expired-sa-account.aspx</id><published>2012-11-11T16:28:00Z</published><updated>2012-11-11T16:28:00Z</updated><content type="html">This is the stuff of DBA nightmares ! email trail: Q. Can you reset the SA account on server XXXXX, we think it has expired and now no-one can work. Connect to Server: Surely no-one would set up a Server with an sa account which expires? Thankfully not. Find sa password and change connection to use SA account. Connect without issue. Me. Have checked Server and account is fine. A. Thanks that&amp;#39;s great, you&amp;#39;ve fixed it we can all work now....(&lt;a href="http://sqlblogcasts.com/blogs/grumpyolddba/archive/2012/11/11/you-couldn-t-write-it-expired-sa-account.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://sqlblogcasts.com/aggbug.aspx?PostID=16330" width="1" height="1"&gt;</content><author><name>GrumpyOldDBA</name><uri>http://sqlblogcasts.com/members/GrumpyOldDBA.aspx</uri></author><category term="File Under Grumpy" scheme="http://sqlblogcasts.com/blogs/grumpyolddba/archive/tags/File+Under+Grumpy/default.aspx" /></entry><entry><title>You Couldn't Write it - Houston we have a problem!</title><link rel="alternate" type="text/html" href="http://sqlblogcasts.com/blogs/grumpyolddba/archive/2012/10/29/you-couldn-t-write-it-houston-we-have-a-problem.aspx" /><id>http://sqlblogcasts.com/blogs/grumpyolddba/archive/2012/10/29/you-couldn-t-write-it-houston-we-have-a-problem.aspx</id><published>2012-10-29T21:16:00Z</published><updated>2012-10-29T21:16:00Z</updated><content type="html">Note identities changed to protect the innocent (sic ). In a datacentre I have an iscsi san which provides storage for a SQL Cluster. It developed a fault and required replacement of a few parts, all hot swappable. Although we had suppport/warranty this did not include onsite so we arranged to have the parts delivered. The datacentre did not want to carry out the work so we had to arrange for the manufacturer to send an engineer. Times were arranged and interested/concerned parties put on standby...(&lt;a href="http://sqlblogcasts.com/blogs/grumpyolddba/archive/2012/10/29/you-couldn-t-write-it-houston-we-have-a-problem.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://sqlblogcasts.com/aggbug.aspx?PostID=16323" width="1" height="1"&gt;</content><author><name>GrumpyOldDBA</name><uri>http://sqlblogcasts.com/members/GrumpyOldDBA.aspx</uri></author><category term="File Under Grumpy" scheme="http://sqlblogcasts.com/blogs/grumpyolddba/archive/tags/File+Under+Grumpy/default.aspx" /><category term="Best Practice" scheme="http://sqlblogcasts.com/blogs/grumpyolddba/archive/tags/Best+Practice/default.aspx" /></entry><entry><title>You Couldn’t Write it !!  ( part 1 )</title><link rel="alternate" type="text/html" href="http://sqlblogcasts.com/blogs/grumpyolddba/archive/2012/10/23/you-couldn-t-write-it-part-1.aspx" /><id>http://sqlblogcasts.com/blogs/grumpyolddba/archive/2012/10/23/you-couldn-t-write-it-part-1.aspx</id><published>2012-10-23T19:41:00Z</published><updated>2012-10-23T19:41:00Z</updated><content type="html">This post was inspired by a developer and I think illustrates the gulf that can sometimes exist between IT and the business. I should point out that this post is the diplomatic version! Initially I was sent a simple search for a person with a question about why the query plan showed a sort when there was no sort in the query and why did the sort show it was 40% of the query. ( The point about the sort belongs to another post some time. ) Easy answer to the duration was that this was a leading wild...(&lt;a href="http://sqlblogcasts.com/blogs/grumpyolddba/archive/2012/10/23/you-couldn-t-write-it-part-1.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://sqlblogcasts.com/aggbug.aspx?PostID=16320" width="1" height="1"&gt;</content><author><name>GrumpyOldDBA</name><uri>http://sqlblogcasts.com/members/GrumpyOldDBA.aspx</uri></author><category term="File Under Grumpy" scheme="http://sqlblogcasts.com/blogs/grumpyolddba/archive/tags/File+Under+Grumpy/default.aspx" /></entry><entry><title>Performance issues due to Inactive Terminal Server Ports</title><link rel="alternate" type="text/html" href="http://sqlblogcasts.com/blogs/grumpyolddba/archive/2012/03/12/performance-issues-due-to-inactive-terminal-server-ports.aspx" /><id>http://sqlblogcasts.com/blogs/grumpyolddba/archive/2012/03/12/performance-issues-due-to-inactive-terminal-server-ports.aspx</id><published>2012-03-12T15:03:00Z</published><updated>2012-03-12T15:03:00Z</updated><content type="html">This is an interesting post and although I don&amp;#39;t have any direct issues of performance with any of my Servers I can see the build up in the registry as described. If you make extensive use of DPR / TS sessions you might want to check this out http://blogs.technet.com/b/askperf/archive/2012/03/06/performance-issues-due-to-inactive-terminal-server-ports.aspx...(&lt;a href="http://sqlblogcasts.com/blogs/grumpyolddba/archive/2012/03/12/performance-issues-due-to-inactive-terminal-server-ports.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://sqlblogcasts.com/aggbug.aspx?PostID=16140" width="1" height="1"&gt;</content><author><name>GrumpyOldDBA</name><uri>http://sqlblogcasts.com/members/GrumpyOldDBA.aspx</uri></author><category term="Diagnostics" scheme="http://sqlblogcasts.com/blogs/grumpyolddba/archive/tags/Diagnostics/default.aspx" /><category term="windows 2008 R2" scheme="http://sqlblogcasts.com/blogs/grumpyolddba/archive/tags/windows+2008+R2/default.aspx" /></entry><entry><title>We all read the instructions first - right ?</title><link rel="alternate" type="text/html" href="http://sqlblogcasts.com/blogs/grumpyolddba/archive/2012/02/09/we-all-read-the-instructions-first-right.aspx" /><id>http://sqlblogcasts.com/blogs/grumpyolddba/archive/2012/02/09/we-all-read-the-instructions-first-right.aspx</id><published>2012-02-09T20:08:00Z</published><updated>2012-02-09T20:08:00Z</updated><content type="html">I&amp;#39;ve been working with the bare metal Hyper V and it&amp;#39;s been an interesting time, if you haven&amp;#39;t ever encountered windows core then it&amp;#39;s a bit of a culture shock, as I understand it SQL Server will be running on windows core very soon - or maybe I read it wrong? Anyway having built my Hyper V server I decided that I&amp;#39;d build a cluster on it, for this you need some shared storage and one way to achieve this is to use Windows Storage Server which in effect creates an iscsi san. So...(&lt;a href="http://sqlblogcasts.com/blogs/grumpyolddba/archive/2012/02/09/we-all-read-the-instructions-first-right.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://sqlblogcasts.com/aggbug.aspx?PostID=16112" width="1" height="1"&gt;</content><author><name>GrumpyOldDBA</name><uri>http://sqlblogcasts.com/members/GrumpyOldDBA.aspx</uri></author><category term="Storage" scheme="http://sqlblogcasts.com/blogs/grumpyolddba/archive/tags/Storage/default.aspx" /><category term="Clustering" scheme="http://sqlblogcasts.com/blogs/grumpyolddba/archive/tags/Clustering/default.aspx" /><category term="windows 2008 R2" scheme="http://sqlblogcasts.com/blogs/grumpyolddba/archive/tags/windows+2008+R2/default.aspx" /><category term="Hyper-V" scheme="http://sqlblogcasts.com/blogs/grumpyolddba/archive/tags/Hyper-V/default.aspx" /></entry><entry><title>x64 Memory Issues - revisited</title><link rel="alternate" type="text/html" href="http://sqlblogcasts.com/blogs/grumpyolddba/archive/2012/01/26/x64-memory-issues-revisited.aspx" /><id>http://sqlblogcasts.com/blogs/grumpyolddba/archive/2012/01/26/x64-memory-issues-revisited.aspx</id><published>2012-01-26T08:19:00Z</published><updated>2012-01-26T08:19:00Z</updated><content type="html">It&amp;#39;s funny how things seem to bob to the surface every so often, a bit like revivals of Musicals or the fact you know it&amp;#39;s christmas becuase ET is on the TV again. Blake Morrision from the Ask the Performance Team has blogged about issues with working sets and SQL Server, http://blogs.technet.com/b/askperf/archive/2012/01/25/real-life-sql-working-set-trimming-issue.aspx ( If you don&amp;#39;t subscribe to this blog then you&amp;#39;re missing a useful source of help ) I blogged about this back in...(&lt;a href="http://sqlblogcasts.com/blogs/grumpyolddba/archive/2012/01/26/x64-memory-issues-revisited.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://sqlblogcasts.com/aggbug.aspx?PostID=16096" width="1" height="1"&gt;</content><author><name>GrumpyOldDBA</name><uri>http://sqlblogcasts.com/members/GrumpyOldDBA.aspx</uri></author><category term="x64" scheme="http://sqlblogcasts.com/blogs/grumpyolddba/archive/tags/x64/default.aspx" /><category term="SQL2008" scheme="http://sqlblogcasts.com/blogs/grumpyolddba/archive/tags/SQL2008/default.aspx" /><category term="x64 Memory and SQL Server" scheme="http://sqlblogcasts.com/blogs/grumpyolddba/archive/tags/x64+Memory+and+SQL+Server/default.aspx" /></entry><entry><title>Q.  When is a HEAP not a HEAP ?</title><link rel="alternate" type="text/html" href="http://sqlblogcasts.com/blogs/grumpyolddba/archive/2011/12/15/q-when-is-a-heap-not-a-heap.aspx" /><id>http://sqlblogcasts.com/blogs/grumpyolddba/archive/2011/12/15/q-when-is-a-heap-not-a-heap.aspx</id><published>2011-12-15T20:56:00Z</published><updated>2011-12-15T20:56:00Z</updated><content type="html">A. When it’s on SQL Server. A very important part of Business Analysis is understanding the perceptions of users even if they haven’t clearly stated a requirement, so a SQL Server table without a clustered index is known as a heap ( in fairness I could say that a table with a clustered index is an ordered heap ), programmers understand heaps as a last in first out “store” ( LIFO ) so if I posed this question &amp;quot; If I put 200 rows of data into a SQL Server table which has no indexes and then select...(&lt;a href="http://sqlblogcasts.com/blogs/grumpyolddba/archive/2011/12/15/q-when-is-a-heap-not-a-heap.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://sqlblogcasts.com/aggbug.aspx?PostID=16027" width="1" height="1"&gt;</content><author><name>GrumpyOldDBA</name><uri>http://sqlblogcasts.com/members/GrumpyOldDBA.aspx</uri></author><category term="File Under Grumpy" scheme="http://sqlblogcasts.com/blogs/grumpyolddba/archive/tags/File+Under+Grumpy/default.aspx" /></entry><entry><title>A follow up to yesterday</title><link rel="alternate" type="text/html" href="http://sqlblogcasts.com/blogs/grumpyolddba/archive/2011/11/22/a-follow-up-to-yesterday.aspx" /><id>http://sqlblogcasts.com/blogs/grumpyolddba/archive/2011/11/22/a-follow-up-to-yesterday.aspx</id><published>2011-11-22T22:02:00Z</published><updated>2011-11-22T22:02:00Z</updated><content type="html">As I have been asked,&amp;#160; here to tidy up yesterdays post is the procedure my startup procedure calls along with the logging table deployed in the DBA database. Just to muddy the water further I have routines for remotely calling the DBAMessages table through a remote server to send out email from a central server!! Just to explain that I have been ( previously ) limited to only using one Server to send email alerts for multiple Servers so I attempt to code to deal with all possible circumstances...(&lt;a href="http://sqlblogcasts.com/blogs/grumpyolddba/archive/2011/11/22/a-follow-up-to-yesterday.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://sqlblogcasts.com/aggbug.aspx?PostID=15976" width="1" height="1"&gt;</content><author><name>GrumpyOldDBA</name><uri>http://sqlblogcasts.com/members/GrumpyOldDBA.aspx</uri></author><category term="Diagnostics" scheme="http://sqlblogcasts.com/blogs/grumpyolddba/archive/tags/Diagnostics/default.aspx" /><category term="Best Practice" scheme="http://sqlblogcasts.com/blogs/grumpyolddba/archive/tags/Best+Practice/default.aspx" /><category term="Monitoring" scheme="http://sqlblogcasts.com/blogs/grumpyolddba/archive/tags/Monitoring/default.aspx" /></entry><entry><title>Hello it’s your server calling</title><link rel="alternate" type="text/html" href="http://sqlblogcasts.com/blogs/grumpyolddba/archive/2011/11/21/hello-it-s-your-server-calling.aspx" /><id>http://sqlblogcasts.com/blogs/grumpyolddba/archive/2011/11/21/hello-it-s-your-server-calling.aspx</id><published>2011-11-21T20:12:00Z</published><updated>2011-11-21T20:12:00Z</updated><content type="html">This is nothing exciting but I&amp;#39;ve always found this startup procedure&amp;#160; very useful. All this simple procedure does is send you an email if the SQL Service Starts. If your Server is a cluster it will tell you which node you&amp;#39;re on. -- On it&amp;#39;s own this procedure can&amp;#39;t actually be used as I route the output through another procedure, dbasp_SendMessage, this procedure routes a passed message to either a smtp email or a log table or both, the destination is set in a server config table...(&lt;a href="http://sqlblogcasts.com/blogs/grumpyolddba/archive/2011/11/21/hello-it-s-your-server-calling.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://sqlblogcasts.com/aggbug.aspx?PostID=15972" width="1" height="1"&gt;</content><author><name>GrumpyOldDBA</name><uri>http://sqlblogcasts.com/members/GrumpyOldDBA.aspx</uri></author><category term="Diagnostics" scheme="http://sqlblogcasts.com/blogs/grumpyolddba/archive/tags/Diagnostics/default.aspx" /><category term="Best Practice" scheme="http://sqlblogcasts.com/blogs/grumpyolddba/archive/tags/Best+Practice/default.aspx" /><category term="SQL2008" scheme="http://sqlblogcasts.com/blogs/grumpyolddba/archive/tags/SQL2008/default.aspx" /></entry></feed>