The ShopClock Network Server Download Page
It is important that the computer chosen for use as the ShopClock server be up and running all the time. It can not hibernate, sleep, or be shut off or the ShopClock clients will not be able to run and will exit with an error message saying they can't connect to the server.
These packages install a "Named Instance", SHOPCLOCK_SS, of Microsoft SQL Server Express, which is used by ShopClock as its network server.
SQL 2017 Express
All the required defaults have been entered into the SQL 2017 Setup package. To install the named instance of SQL 2017 Express for use as the ShopClock network server all you need to do is run this package, agree to Microsoft’s terms, and accept all the preloaded default values by clicking next at the bottom of each screen.The install is interactive, so things like where the data is stored can be changed if needed.
If the above installer does not work, you can unziip the contents of this file and then run the batch command
The ShopClock database will be created in the SHOPCLOCK_SS server when the ShopClock client is connected to the server for the first time.
Or download Sql 2017 directly from Mirosoft https://www.microsoft.com/en-us/download/details.aspx?id=55994
Be sure to enable the features listed below under the SQL 2012 express.
SQL 2017 Requirements
SQL 2017 is a 64-bit program and can’t be installed on 32 bit machines. Here is a list of the supported operating systems.
Windows Server 2016 Datacenter
Windows Server 2016 Standard
Windows Server 2016 Essentials*
Windows Server 2012 R2 Datacenter
Windows Server 2012 R2 Standard
Windows Server 2012 R2 Essentials
Windows Server 2012 R2 Foundation
Windows Server 2012 Datacenter
Windows Server 2012 Standard
Windows Server 2012 Essentials
Windows Server 2012 Foundation
Windows 10 Home
Windows 10 Professional
Windows 10 Enterprise
Windows 10 IoT Enterprise
Windows 8.1 Pro
Windows 8.1 Enterprise
Windows 8 Pro
Windows 8 Enterprise
Installing SQL Server on a Domain Controller
For security reasons, Microsoft recommends that you do not install SQL Server on a domain controller. SQL Server Setup will not block installation on a computer that is a domain controller, but the following limitations apply:
• You cannot run SQL Server services on a domain controller under a local service account.
• After SQL Server is installed on a computer, you cannot change the computer from a domain member to a domain controller. You must uninstall SQL Server before you change the host computer to a domain controller.
• After SQL Server is installed on a computer, you cannot change the computer from a domain controller to a domain member. You must uninstall SQL Server before you change the host computer to a domain member.
• SQL Server failover cluster instances are not supported where cluster nodes are domain controllers.
• SQL Server is not supported on a read-only domain controller. SQL Server Setup cannot create security groups or provision SQL Server service accounts on a read-only domain controller. In this scenario, Setup will fail.
• A SQL Server failover cluster instance is not supported in an environment where only a read-only domain controller is accessible.
SQL 2012 Express
These are hybrid installation packages that can be used on both 32 and 64 bit computer
Requirements for SQL 2012
- For Windows 7 or Windows Server 2008 R2, Service Pack 1 or later is required.
- For Windows Vista or Windows Server 2008, Service Pack 2 or later is required.
- For more info see http://go.microsoft.com/fwlink/?LinkID=195092
Supported Operating Systems for SQL 2012:
- Windows 7, 8, 8.1, 10
- Windows Server 2008 R2 and newer
- Do not install this on a Domain Comptroller. See KB2032911 http://support.microsoft.com/kb/2032911
- (If you are using XP as a server, download MSSQL 2005 from the bottom of this page).
Scripted vs Interactive SQL Server Installation
The Scripted installation runs without asking for any input. Everything is installed in the default locations on drive c. The interactive installation give you the opportunity to put things where you want, but some settings are required for ShopClock to use the database. See the interactive instructions below.
Download and save it (scSqlServer2012Sp1Setup.exe) to your server's desk top, and after it's downloaded, double click on it to install the named instance (SHOPCLOCK_SS) of Microsoft SQL 2012 Server on your computer. That's it, no wizard, no decisions. Just wait until it finishes installing.
Use this to Upgrade SQL Server 2005 to 2012 or do a custom Installation of SHOPCLOCK_SS.
Download the interactive version. The interactive version gives you the choice of either upgrading an existing SQL instance to 2012 or of doing a new install.
To Upgrade MS SQL 2005 to 2012, just click on the UPGRADE button and follow the on-screen prompts. If you upgrade an existing 2005 ShopClock instance of MSSQL to 2012, you must also recreate the Auto Backup Devices on tab 11 (Backup/Restore Database) of the Admin window. Also be sure to install the latest version of ShopClock4 or ShopClock4Plus on the server. This later step is necessary for restoring the database. ShopClock3 can not restore the database to the 2012 instance - you must use ShopClock4 or 4plus.
To do a Custom Installation of the SHOPCLOCK_SS instance, click on the New Install button.
When doing a custom installation of the SHOPCLOCK_SS instance you must include the following settings. Settings like where things are installed are up to you.
- /[email protected]!
After the ShopClock Server has been installed
- Bring ShopClock's Admin Window up and click on the 'Edit Network Database' button. Refresh the server list, select this server, and click OK. ShopClock will finish configuring the network database and will then copy the local database up to the server
- Check your firewall settings. If you are using a fire wall, ei
- then turn it off or add exceptions for SQL Server. See Accessing the Network Database.
If you must Use a Windows XP Computer as the Server
Download ShopClock Network Server MS SQL 2005 Express Service Pack 4 (sqlSvr2005Sp4Setup.exe)