Introduction > Creating Alerts and Reports > Conditional Alerts > Alert Conditions > Database Conditions

Before you can use a Database Alert Condition in one of your WinScry Conditional Alerts you have to create a SQL Connection Profile. The connection profile defines the type of SQL Server you are using (Microsoft SQL Server, MySQL, or ODBC), as well as the database name and authentication methods to use.

IMPORTANT NOTE FOR MYSQL: WinScry was certified for MySQL Version 5.6 and greater. If you are using earlier versions of MySQL we can only recommend that you try it first and verify that the connectivity and Query options work for you OR create an ODBC DSN and use an ODBC profile (see below)

Database Connections

Select a Connection

Two Different Ways to Open the SQL Connection Profiles Window

You can get to the SQL Connection Profiles window two different ways. Either from the Tools menu in the main window OR in the SQL Database Alert Condition window (click the screenshots to the left to expand). This will open the SQL Server Connection Profiles window. From the SQL Connection Profiles window you can Select / Create / Edit / Delete database connection profiles. Depending on where you open the connection profiles window FROM (the main window tools menu or the Alert condition window) you will see a slightly different variation of the screen with slightly different options.

Accessed from the Main Window Tools menu

From the Tools menu (Click to Zoom)

SQL Server Connection Profiles Window

If accessed from the main window Tools menu

When accessed from the Tools menu on the main window you will note that for existing connection profiles you have two option buttons (see the screenshot to the left).

•Press the F2 Key. To create a new profile.

•Edit. To modify an existing SQL Connection Profile.

•Delete. To permanently delete an existing SQL Connection Profile.

Accessed from the Database Alert Condition Window

Database Alert Window (Click to Zoom)

SQL Server Connection Profiles Window

If accessed from the Database Alert Condition Window

When accessed from the Database Alert Condition window you will note that you will have different options than if accessed via the main window (see the screenshot to the left).

•Select. To select the SQL Connection Profile to use in your Database Alert Condition.

•Edit. To modify an existing SQL Connection Profile.

•Press the F2 Key. To create a new profile.

Creating SQL Connection Profiles

No matter how you access the SQL Server Connection Profiles window you can create new connection profiles by either pressing the F2 key OR selecting New Connection Profile from the File menu. This will open up the RDBMS Connection Profile window which allows you to create (or modify if you clicked an Edit button) a SQL Connection Profile.

MS SQL Server (Click to Zoom)

Microsoft SQL Server Connection Profiles

To create a connection profile for MS SQL check the Microsoft SQL Server button. Then enter the connection parameters which WinScry should use:

•SQL Server Name: The name of your MS SQL Server. HINT: In the MS SQL Server management studio you can RIGHT CLICK on the Server Connection and look at the Properties to get this value.

•Database Name: The name of the MS SQL Database.

• Authentication / Security: This is an IMPORTANT decision. Here you have 2 options SQL Server User ID or Windows Logon (Trusted). We recommend that (if possible) you use the SQL Server User ID option, if you do choose Windows Logon (Trusted) then you should review the topic on Running as a User to see if it will impact the WinScry Windows Service. If you choose SQL Server User ID, enter your SQL User ID and Password in the appropriate fields.

•Database Connection Timeout: 30-45 seconds are good general purpose values. This value not only determines how long an attempt by WinScry to connect to the server will be allowed but also will be used as the timeout value for SQL Queries you use in your Database Alert Conditions that use this connection.

•Use Microsoft SQL Server Connection for Azure: Is only applicable if you are working on a local computer which needs to access a database in the Microsoft Azure Cloud.

After entering all data click the Test the connection to the SQL Server / Database button to test your connection profile. When completed click the OK button to save your connection profile.

MySQL Connection (Click to Zoom)

MySQL Connection Profiles

To create a connection profile for MySQL check the MySQLbutton. Then enter the connection parameters which WinScry should use:

•SQL Server Name: The name or IP address of your MySQL server.

•Database Name: The name of the MySQL Database.

•MySQL Force SSL: Is only applicable if you have enabled SSL in your MySQL server.

•Specify MySQL Port Number: (Optional) If you are using a port other than the MySQL default port you can check the Specify MySQL Port # box and then enter the MySQL Port Number

After entering all data click the Test the connection to the MySQL Server / Database button to test your connection profile. When completed click the OK button to save your connection profile.

ODBC Connection (Click to Zoom)

ODBC Connection Profiles

To create a connection profile for an ODBC database check the ODBC button. Then enter the NAME of the DSN which WinScry should use. You can click one of the buttons shown to open the appropriate ODBC Manager to see all of your DSNs or create new ones.

IMPORTANT NOTES ABOUT USING ODBC DRIVERS (64-Bit and 32-Bit)

1.MS Windows can be tricky when it comes to using ODBC drivers. The ODBC Driver and DSN must match your architecture. As an example let's use ORACLE. If your system is a 64-Bit system then you should install the 64-Bit version of the WinScry Client Console, correct??? Not so fast. If you only have a 32-Bit ORACLE ODBC driver then you would need to install the 32-Bit version of the WinScry Client Console because the 64-Bit version (even though it is more native) cannot use cannot use DSNs created with 32-Bit only ODBC drivers. To use the 64-Bit version of the WinScry Client Console with ORACLE you would have to procure a 64-Bit ORACLE ODBC Driver.

2.When you create your ODBC DSN(s) we strongly recommend that you use SYSTEM DSN(s) as these are the only types which were used to certify the ODBC functionality of the WinScry Client Console. USER DSN(s) may also work but if used you will likely need to make sure that the the WinScry Windows Service runs as a domain user (see Running as a User).

After entering the name of the DSN click the Test the connection to the ODBC Database button to test your connection profile. If the connection test is successful click the OK button to save your connection profile.