Sql Server

Category: Database Connectors

Introduction

This document is created to help setup a mindzieDataDesigner connector to Microsoft SQL Server database. The mindzieDataDesigner is the ETL tool used by mindzieStudio to convert database tables to process mining event logs. The purpose of this document is to help creating the connection string and opening ports on the firewall if required.

Overview

The Microsoft SQL Server connector provides native connectivity to SQL Server instances, offering high performance and full feature support. This connector is optimized for enterprise environments and supports all SQL Server versions from 2012 onwards.

System Requirements

• Database System: Microsoft SQL Server 2012 or later
• Supported Editions: Express, Standard, Enterprise, Developer
• Platforms: Windows Server, Linux (SQL Server 2017+)
• Cloud Support: Azure SQL Database, Azure SQL Managed Instance
• Dependencies: Uses native SQL Server client drivers

Connection String Format

Standard SQL Server Authentication

Server=server_name;Database=database_name;User ID=username;Password=password;

Windows Authentication

Server=server_name;Database=database_name;Integrated Security=true;

Connection Parameters

Parameter	Description	Required	Example
Server or Data Source	SQL Server instance name/IP	Yes	localhost\SQLEXPRESS
Database or Initial Catalog	Database name	Yes	MyDatabase
User ID	SQL Server username	No*	sa
Password	SQL Server password	No*	MyPassword123
Integrated Security	Use Windows Authentication	No	true or SSPI
Connection Timeout	Connection timeout (seconds)	No	30
Command Timeout	Command timeout (seconds)	No	600
Encrypt	Enable SSL/TLS encryption	No	true or false
TrustServerCertificate	Trust server certificate	No	true or false
ApplicationName	Application identifier	No	mindzieDataDesigner

*Required unless using Integrated Security

Connection Examples

Local SQL Server Express

Server=localhost\SQLEXPRESS;Database=ProcessMining;Integrated Security=true;Connection Timeout=30;

SQL Server with Authentication

Server=sql-server.company.com;Database=ProcessMining;User ID=mindzie_user;Password=SecurePassword123;Encrypt=true;TrustServerCertificate=false;

Azure SQL Database

Server=tcp:myserver.database.windows.net,1433;Database=ProcessMining;User ID=mindzie_user@myserver;Password=SecurePassword123;Encrypt=true;TrustServerCertificate=false;Connection Timeout=30;

SQL Server with Custom Port

Server=192.168.1.100,1435;Database=ProcessMining;User ID=mindzie_user;Password=SecurePassword123;

High Availability (Always On)

Server=tcp:ag-listener.company.com;Database=ProcessMining;User ID=mindzie_user;Password=SecurePassword123;MultiSubnetFailover=true;

Authentication Methods

Windows Authentication (Recommended for Domain Environments)

• Uses current Windows user credentials
• No password storage in connection strings
• Supports Active Directory integration
• Best for internal corporate environments

SQL Server Authentication

• Uses SQL Server native login accounts
• Requires username and password in connection string
• Works across different platforms and networks
• Suitable for web applications and external access

Azure Active Directory Authentication

Server=tcp:myserver.database.windows.net;Database=ProcessMining;Authentication=Active Directory Integrated;

Troubleshooting

Common Connection Issues

"Login failed for user" Error

• Verify username and password are correct
• Check if the user account is enabled and not locked
• Ensure the user has permission to access the specified database
• For Windows Authentication, verify the account has login rights

"Server not found or not accessible" Error

• Verify server name and port number
• Check network connectivity and firewall settings
• Ensure SQL Server is running and accepting connections
• Verify SQL Server Browser service is running (for named instances)

"Timeout expired" Error

• Increase Connection Timeout value
• Check network latency and stability
• Verify server resources and performance
• Consider query optimization for large datasets

"Certificate chain was issued by an untrusted authority" Error

• Set TrustServerCertificate=true for development environments
• Install proper SSL certificates for production environments
• Use Encrypt=false only in secure internal networks

Azure SQL Considerations

Azure SQL Database

• Use fully qualified server names: server.database.windows.net
• Always use encrypted connections
• Consider firewall rules and IP restrictions

mindzie Server Access: For enhanced security, you can configure your firewall to only allow connections from mindzie servers by whitelisting specific IP addresses. Contact mindzie support to obtain the current IP addresses for the mindzie servers you are using.

Connection Resilience

Server=tcp:myserver.database.windows.net;Database=ProcessMining;User ID=user@myserver;
Password=password;Encrypt=true;Connection Timeout=30;ConnectRetryCount=3;
ConnectRetryInterval=10;

Related Information

• Official Documentation: Microsoft SQL Server Documentation
• Azure SQL: Azure SQL Database Documentation
• Connection Strings: ConnectionStrings.com - SQL Server
• Security: SQL Server Security Best Practices

---

💡 Tip: For enterprise deployments, consider using Windows Authentication with service accounts for enhanced security and easier credential management.