When the network option is added to HORTICOPIA® Professional, an SQL Server is required. The standalone version of HORTICOPIA® Professional utilizes the Microsoft SQL Local database software package which does not require a separate standalone SQL Server installation. However, the standalone version of HORTICOPIA® Professional will also work with a separate SQL Server, although we do not recommend this approach.
The remainder of this memo discusses the networked HORTICOPIA® Professional requirements for an SQL Server. This is not a "how-to" tutorial. It simply states the HORTICOPIA® Professional requirements for the SQL Server and provides guidance on where you can obtain the Microsoft tools that will meet these requirements.
HORTICOPIA® Professional software has been tested with Microsoft SQL Servers 2005, 2008, 2012, and 2014. It may work with other, non-Microsoft SQL servers as well, but we cannot offer any support for these configurations.
If you do not already have a Microsoft SQL Server installed, you can get Microsoft SQL Server Express free of charge from Microsoft's website, www.microsoft.com.
If you are running Windows Server 2008 or 2012, you can use SQL Server 2008 or 2012. We highly recommend that you also download and install the Microsoft SQL Server Management Studio Express (SSMSE). Some of the SQL Express Server downloads already include SSMSE
The SQL Server Management Studio provides extensive online help.
HORTICOPIA® Professional supports SQL Servers anywhere on the network. Configuration of HORTICOPIA® Professional is simpler when the SQL Server and HORTICOPIA® Professional are located on the same server.
If you do not have the default instance of SQLEXPRESS installed, you should create a new SQL Server instance. You may call it HORTPROSQL or any other name of your choosing although both HORTPROSQL and SQLEXPRESS are automatically searched for by HORTICOPIA® Professional.
Be sure the TCP/IP protocol is enabled for the Network Protocols. By default, the SQL Server installation does not enable it. Use the SQL Server Configuration Manager for this task.
In the SQL Server Configuration Manager, make sure the Browser service is enabled and running.
If you have a firewall (including Windows firewall) you must allow both the SQL Server and the Browser services as firewall exceptions.
HORTICOPIA® Professional requires read/write/update rights to the HORTICOPIA database. Generally, access rights are given to users of an instance of the SQL Server, but may be given to just a specific database..
You should first run HORTICOPIA® Professional on your Server to make sure it works with your SQL Server. You should run with an Administrator account first and then fine-tune the access privileges.
Use the SSMSE and connect to the SQL Server instance you're using for HORTICOPIA® Professional. In the Security section, add the users (or groups) that should have access and give them SYSADMIN rights. If you wish to be more restrictive, attach the Horticopia database first and then give only db_datareader and db_datawriter rights.
You may get "untrusted domain" errors on your client computers if you add users as described for Domain Users. To get around this, create a new SQL Server authentication login and give it the appropriate rights. Enter the user ID and password in the HORTICOPIA connection section of the horticopia.ini file.
The best approach to troubleshooting connections from the client is to install SSMSE on the client. Try to establish a connection to the SQL Server. Once you've established a connections, see if you can attach the HortData database. Once this can be accomplished, HORTICOPIA® Professional should be able to connect from the client workstation.
« Go back
Powered by Help Desk Software HESK - brought to you by Help Desk Software SysAid