Tag Archives for " Pro Advice "

Jun 01

SQL Server 2016 RTM Available!!

By SQLRx Admin | Advice , Installation , Miscellaneous , SQL Server , Upgrade

In case you live under a rock or were at the dentist, Microsoft announced that SQL Server 2016 has been made generally available today June 1, 2016. See: https://blogs.technet.microsoft.com/dataplatforminsider/2016/06/01/sql-server-2016-is-generally-available-today/ Pricing is as follows: A handy feature comparison of previous versions of SQL can be located here: https://www.microsoft.com/en-us/server-cloud/products/sql-server/comparison.aspx SQL 2016 feature comparison between editions can be […]

Continue reading
May 19

Correlate Performance Spikes with SQL Profiler and Perfmon

By Ginger Daniel | Intermediate , Perfmon , Performance Tuning , SQL Server , SQLRX

–by Ginger Keys Have you ever watched performance metrics in Performance Monitor (Perfmon) and wondered which SQL Server activities were causing those spikes? SQLRx offers a Microsoft Partner-of-the-Year award-winning service that will correlate all performance metrics on your server with very little overhead, and will pinpoint with precision, right down to a line of code […]

Continue reading
Mar 09

March 2016 Tip of the Month -Full Text Indexing – Clean up those log files!

By SQLRx Admin | Advice , Beginner , Miscellaneous , SQL Administration , SQL Server , Tip of the Month

If you have Full Text catalogs set up in your databases you may notice that inside your log folder there will be lots of files named SQLFTxxxxxxxxxxxx.LOG. These are known as crawl logs which are designed to log information on the full text indexing. These logs can really pile up and there is no automated […]

Continue reading
Jan 07

Disk Metrics – Why PerfMon’s, SQL Server’s Filestats, and Disk Vendors’ Values Sometimes Appear to Disagree

By Jeffry Schwartz | Expert , Performance Tuning , SQL Server , Windows

— By Jeffry Schwartz Whenever multiple data sources are used, actual or perceived discrepancies can arise. Sometimes this is due to the location of the data collector, e.g., Windows, SQL Server, or the disk array. Other times, it is due to the collection rate and whether the information is a simple recording of continuously incremented […]

Continue reading
>