[dba-SQLServer] dba-SQLServer Digest, Vol 147, Issue 1

[David Lewis]

There is little information to go on without any monitoring tools.  That it seems to coincide with users making menu selections, suggests that there MAY be very ill-advised queries used to deliver a convenient human-consumable list.  The number of things to look out for are too many to list (query operators, that is).  Another item to consider is deadlocks -- if the same resources are being used (tables, etc.), and the queries are not well constructed, there is a good chance that there are page or row locks occurring, which will bring a db to its knees without intervention.

No simple answer to this.  Using access as a front end with sql express implies that the company is too cheap/ignorant to buy a monitoring tool.  As you say there is nobody inhouse with the skills to do it the hard way (using the wait stats etc. admin tools in sql server).


------------------------------

Message: 3
Date: Tue, 12 Apr 2016 13:20:10 -0400
From: J- P <jnatola at hotmail.com>
To: sql list <dba-sqlserver at databaseadvisors.com>
Subject: Re: [dba-SQLServer] DB growth spurt/Comparison tool
Message-ID: <BLU185-W4097B70865355047DED043BC950 at phx.gbl>
Content-Type: text/plain; charset="iso-8859-1"

I agree with the execution plan and queries, however, I'm running into a brick wall because I am NOT qualified to look at these queries, hash joins, or execution plans and see where they are flawed, and the "DBM" refuses to acknowledge it and  says "it's lack of resources we need full SQL"

I told them  sure you can throw money at the problem , but that's addressing the symptoms not addressing the cause.


________________________________

The contents of this e-mail message and its attachments are covered by the Electronic Communications Privacy Act (18 U.S.C. 2510-2521) and are intended solely for the addressee(s) hereof. If you are not the named recipient, or the employee or agent responsible for delivering the message to the intended recipient, or if this message has been addressed to you in error, you are directed not to read, disclose, reproduce, distribute, disseminate or otherwise use this transmission. If you have received this communication in error, please notify us immediately by return e-mail or by telephone, 530-893-3520, and delete and/or destroy all copies of the message immediately.