When managing SQL Server there are so many different places to look for data. These include the error logs, system event logs, logs saved as SQL tables, etc... Once you have collected the data, you then need to parse through and interpret the data you collected.
Monitoring Microsoft SQL Server with Loom Systems gives you critical visibility into what’s happening with your database and the applications that depend on it. Loom Systems allows you to view the health of your servers without manual setup and delays. It will show you which servers have been stopped, the error log types over time, top errors, top warnings, crash recovery attempts over time, and the count of how many times a server has been up or down in a specific time window. In addition, if you are auditing logins these messages are also stored in the error log, so this further compounds the problem.
Using SQL DB to store your unstructured proprietary logs? Simply stream the logs tables to Loom Systems in less than 2 minutes.
● Automatically monitor server performance, detect issues and changes over time
● Correlate between different layers of your application
● Analyze proprietary unstructured logs saved in your MSSQL DB
Check out Loom Systems to identify patterns of errors associated other issues to improve the performance of your MSSQL database server. It is included with your free trial. Register now to get started!
Configuration that requires less than 5 minutes, will enable you to see the all events you need. Loom Systems will process your SQL server Error Logs and proprietary application logs. Loom will transform your data into insightful information. Far beyond a simple aggregation of your Logs, Loom lets you:
Monitor across disparate sets of SQL tables data and uncover hidden business opportunities and issues
Be alerted to any abnormal customer sessions and behavior, with correlations across your data base and other parts of the application tier (for example slow query responses)
Discover and resolve bottlenecks in your application in real time
Investigate any activity, drill down to the smallest activities in any time frame
Loom Systems is the only solution which enables you to collect any logs format from any table with in your Microsoft SQL DB. Simply use the "Microsoft SQL Server" Plug in and start to gain insights into your application.
The Error Log, the most important log file, is used to troubleshoot system problems. SQL Server retains backups of the previous six logs, naming each archived log file sequentially. The current error log file is named ERRORLOG. Simply configure nxlog on your sql server and loom will immediately process your error logs.
By default, the error log is located at Program Files\Microsoft SQL Server\<Key_Name>\MSSQL\LOG\ERRORLOG and ERRORLOG.n files.
Note that “<Key_Name>” would vary based on SQL Server Version and instance name which is installed.
In SQL Server 2005, we would see a key name in the format of MSSQL.n (like MSSQL.1) the number n would vary based on instance ID.
When SQL Server is configured to use the Microsoft Windows application log, each SQL Server session writes new events to that log. Unlike the SQL Server error log, a new application log is not created each time you start an instance of SQL Server.
*The ERRORLOG uses UTF-16LE encoding
TIP: If you go to server properties, in the database settings, you will find the default database data, log and backup locations:
Microsoft SQL Server is an RDBMS (relational database management system) developed by Microsoft. Ranging from small single-machine applications to large high-scale applications.
Loom Systems monitors SQL Server databases across all platforms and analyzes the activity of your database services, providing visibility down to individual MSSQL commands.
Further details about Microsoft SQL server logs can be found here.