Some Kronos SQL Server Tips from Experience

Your web browser is out of date. Update your browser for more security, speed, and the best experience on this site.

You may also visit the site on your mobile device.

Some Kronos SQL Server Tips from Experience


I'd like to welcome Ken Lassesen from Microsoft's SQL Server blog to our writing pool. Below is a preview of an article he's written for all the Kronites out there.


How should one design and build Kronos interfaces?

What's the best approach to interfacing Kronos and my ERP? Should one use Connect/WIM or SQL? Integration Guru Eugene Harrison has an opinion.

Download the Kronos Interface Design Strategy White Paper Now!


Recently I had a conversation with Bryan deSilva, Chief Evangelist of Improvizations, a firm that specializes in workforce management software implementations. He is an active blogger on Kronos (here). During our short chat, he identified one common installation problem he has seen which I will provide a visual step-by-step solution to.

Installation Issue: SQL Server needs TCP/IP Enabled for Kronos

To check this is a simple process:

  1. Click Start / Program and you will find a ‘SQL Server Configuration Manager’ under Microsoft SQL Server (2005/2008) / Configuration Tools as shown.

  2. This will open up the application as shown below

     SQL Server Configuration Manager for Kronos
  3. Click on ‘SQL Server Network Configuration’ and identify the Server Instance that is running Kronos, for example ‘ECOMMERCE’, then double click

    SQL Server Network Configuration 

  4. You will see ‘TCP/IP’ listed under the Protocol Name, the status should be ‘Enabled’

describe the image
a. If not, then select TCP/IP and right click. This will bring up a menu, select ‘Enable’


b. You will then see a message telling you to stop and restart SQL Server. 

Best practice is to disable both Named Pipes and VIA.  You may wish to disable ‘Shared Memory’ to give SQL Server more resources.


Ken Lassesen, Consulting ISV Architect

Ken's first programming experience was with APL/360 at the University of Waterloo in 1968. Before Microsoft conscripted him as an employee for the original MSDN writing team in 1994, he had consulted to Microsoft since 1991. Involvement with the first alphas of Microsoft SQL Server 4.2 earned him the nickname of "Dr.Science" for his analysis of performance issues. Leaving Microsoft in 2000, he worked for Satyam and a number of startups. He returned as a consultant to Microsoft in 2003 for He has consulted to ISVs (Lumension / Patchlink, Blackboard), startups and been involved with several NIST groups (SCAP, OVAL and RBAC). Ken holds a M.S. (Business Administration) specializing in Information Management and Optimization.

Ken is married and lives in Bellingham, WA.  He has three daughters and one Corgi (Panda). An active hiker with many trail reports on Washington Trail Association.



YouTube Icon LinkedIn Icon Twitter Icon