#Hmail change mysql database server code
Well, Stuart wrote some nifty code to check how out-dated your SQL Server stats may be, across all tables and all databases in your server. I mentioned briefly above how outdated SQL Server statistics can hurt, as they're used by the query analyzer to create execution plans. While he has hundreds of posts each year that are valuable, one in particular that I find myself pointing people to is one done actually by a guest blogger, Stuart Ainsworth (who I've known from our days in the Atlanta SQL Server user group, ). Showing outdated SQL Server statistics: Second is a post on the blog of a really great daily SQL blogger, Pinal Dave (A former CFer) who runs the SQLAuthority blog.And if there is not, then it points to a possible networking issue, in CF's inability to talk to the DB server. Being able to confirm if there IS a query running at such time can be valuable. Sometimes SQL Server monitoring tools may NOT show any queries running at a point in time, when your own observation of an app, or better monitoring tools for ColdFusion (or whatever app server you use) may say that they ARE waiting for the DB to finish some long-running query or stored procedure. Showing long-running SQL Server queries: First is a post of my own, Free, simple code to find out what SQL statements are running slow in SQL Server right now, with some SQL code that helps you readily see what queries are running right now.I'm correcting that dangling preposition at end of the section title just then.) People using other DBs would do well to read along and could find corresponding resources/tools for the same problems in their respective DB servers.įirst up, I want to list here some blog posts to which I often find myself referring people. Some are blog posts, some are code you can run, and some are tools (mostly free). So in this post I want to focus on some SQL Server resources, related to such matters, which I find that I refer folks to often.
#Hmail change mysql database server windows
Or it may be that they have not done any tuning at all and the default settings for their database server are not be well suited to them.Īnd though such problems are common to any database server (MySQL, Oracle, PostgreSQL, and so on), I find that an awful lot of my clients (for whatever reason) do run on Windows and do use SQL Server (and that doesn't make them stupid or lazy. For instance, it may be that they have not been keeping their indexes or statistics updated, or it may be that they need indexes that they don't have, or have too many that they don't really need. More often it's about configuration issues.
Often in my role as an independent consultant providing ColdFusion server troubleshooting services, I find myself helping folks determine whether or that a problem is in their database.Īnd though it may surprise many, I generally do not find the problem to be very often with the SQL they are running. And I may revise the content as necessary.
Corrections are welcome, in the comments. Same with links and subsequent comments from myself or others. Some content may be outdated-though not necessarily.
0 kommentar(er)
