Support for Advanced SQL Database Setups

Randall Berg -

 

Does your SQL database have multiple instances or use a non-standard TCP port for a connection?  If so, this document may provide some useful workarounds to getting up and connected!

 

 

Multiple Instances

If you are running multiple instances of SQL Databases on your machine, you'll need to specify the instance when adding the datasource into BrightGauge.  depending on your SQL database type (Microsoft or mySQL), there are two ways you can do it:

 

Add the instance name into the Database IP field:

192.168.1.100/instance1

machinenamex/instance 1

 

If the above doesn't work, try adding it to the database name field:

instance1/ksubscribers

instance1/cwwebapp_brightgauge

 

 

Non-Default TCP Port

If your SQL setup is using a non-default TCP (Microsoft SQL is 1433, mySQL is 3306), you'll need to add the port information into the Database IP field under your datasource settings page on your account.  This can sometimes change so, please try both variations using a colon or a comma:

 

Colon

Using IP =  192.168.1.100:1900

Using Machine Name = machinenamex:1900

 

Comma

Using IP = 192.168.1.100,1900

Using Machine Name = machinenamex,1900

 

 

Dynamic Ports Enabled (Microsoft SQL)

If the database you're using has Dynamic Ports enabled with a value in the field and no value in the TCP Port field

dynamic_port.png

 (screenshot from SQL Server Configuration Manager -> SQL Server Network Configuration -> Protocols for ServerName -> TCP/IP -> IP Addresses -> scroll to bottom)

You'll need to put a value in the TCP Port field.  The default TCP Port for Microsoft SQL is 1433.

dynamic_port_2.png

IF you have multiple instances and the non-BrightGauge instance is using port 1433 and you setup the BrightGauge instance to use port 1433, you'll break your setup.  Instead assign the BrightGauge instance to use a different port and then follow the Non-Default TCP port steps above to get your SQL database connected to BrightGauge.

If you make any changes here, you'll need to restart the SQL Server.  This will temporarily take down any connections to the database, so you might want to wait to do this until off hours.  To restart the server, in the SQL Server Configuration Manager, go to the SQL Server Services section identify your SQL Server service name SQL Server (ServerName), right click on it and click on restart.

 

Of course if you're still having issues after this, we'd be glad to help, just shoot us a line at support@brightgauge.com with your SQL server details and we'll get right on it.

Have more questions? Submit a request

Comments

Powered by Zendesk