Set up or choose your SQL Server

Start with a running SQL Server, then add the Windows tools used to prepare Northwind and load the warehouse. You can use an existing server or install Developer for this exercise.

Choose your SQL Server

1. Open the setup record and choose one of the two routes below. Record the server address, version and sign-in method as you prepare them. Keep passwords in your password manager.

Use SQL Server 2019 or newer, with a deployment target supported by your AnalyticsCreator release. Microsoft's latest engine is SQL Server 2025; the deployment choices in AnalyticsCreator 3.8.0.15 extend through SQL Server 2022. For the concrete installation below, use SQL Server 2022 Developer. Use a newer engine once a matching deployment path is confirmed for your AnalyticsCreator release. Developer is an edition of SQL Server; it can run on your computer or another Windows computer. You do not need to reinstall a suitable existing server.

Route A. Use an existing Windows SQL Server

1. Obtain the actual server and instance name, or server address and TCP port, from the SQL Server administrator. For an instance on this computer, an example is localhost\ACLAB. For another computer, use its actual network name, such as TRAINING-PC\ACLAB, or its supplied TCP address.
2. Confirm the engine version and a matching AnalyticsCreator deployment target before choosing this server. This guide uses the SQL Server 2019 or 2022 target as appropriate; for a newer engine, confirm its supported deployment path with AnalyticsCreator first. Arrange an isolated Northwind tutorial database and permission to prepare separate warehouse databases. Keep other databases and other people's work unchanged.
3. Record whether you will use Windows authentication or a SQL Server login. For a server on the local network, have its administrator allow this Windows computer to connect.

With the server details ready, prepare the Windows tools.

Route B. Install SQL Server Developer

Use a Windows computer that meets Microsoft's SQL Server 2022 requirements, with administrator access for installation. The Windows SQL Server engine is 64-bit; there is no 32-bit engine choice for this tutorial.

1. Download SQL Server 2022 Developer from Microsoft for this non-production tutorial. It matches the 2022 deployment target used below. Microsoft's current SQL Server download page also shows the latest engine release; confirm AnalyticsCreator deployment support before choosing a newer one.
2. Open the Microsoft installer and choose the custom installation path. In SQL Server Installation Center, select Installation, then New SQL Server standalone installation or add features to an existing installation.
3. Review the license and setup checks. On Feature Selection, select Database Engine Services. The loading tools are installed separately below.
4. On Instance Configuration, choose an unused instance name, for example ACLAB. Record the resulting connection name, such as localhost\ACLAB.
5. On Database Engine Configuration, use Windows authentication mode for this local setup and select Add Current User. Keep the database folders assigned to this instance.
6. Review Ready to Install, select Install and wait for completion. Resolve any failed component in the setup summary and restart Windows if requested. Record the installed release and instance name.

Result: Database Engine installation completed successfully. Microsoft's installation walkthrough covers additional setup screens.

Prepare the Windows tools

Both server routes use the same tools below. SQL Server Management Studio (SSMS) manages databases. Integration Services (SSIS) runs the generated loading files. The database engine and the loading program can be on different computers.

2. Install the latest SQL Server Management Studio on the computer you will use for the tutorial. Download vs_SSMS.exe, open it and select Install in Visual Studio Installer. Current SSMS uses supported 64-bit Windows; Microsoft does not offer a current 32-bit SSMS installer.
3. Choose the Windows computer that will run the loading files. It must reach Northwind and the warehouse. This guide uses Integration Services 2022 with SQL Server 2022 package compatibility. Its loading-program version is separate from the database engine and its deployment target.
4. If Integration Services 2022 is missing, obtain SQL Server 2022 Developer installation media for this learning setup. In its Installation Center, select the new installation/add-features option, then Integration Services under shared features. Complete setup using Microsoft's SSIS installation instructions. A second Database Engine is unnecessary on a separate loading computer. The SQL Server 2025 installer does not install the 2022 loading program.
5. Open Windows PowerShell on the loading computer. Run the command below to display the loading program's help and version. If you installed it elsewhere, replace the path with its actual location.

   & 'C:\Program Files\Microsoft SQL Server\160\DTS\Binn\DTExec.exe' /?

   Expected result: Microsoft package execution utility help and version 16.x. Record the exact path and version. This command does not load data.

6. Open Microsoft's OLE DB Driver download page and install 19.4.2 on the AnalyticsCreator and loading computers. This tutorial uses the provider name MSOLEDBSQL19. Use the architecture choice below and install the Visual C++ prerequisites listed by Microsoft.

   Official download	When to use it
   Driver 19.4.2, x64 / Arm64	Use the x64 installation on the 64-bit Intel/AMD Windows computer used in this guide. On x64 Windows it supplies both 64-bit and 32-bit driver binaries. Install both the x64 and x86 Visual C++ prerequisites; you do not need both driver installers.
   Driver 19.4.2, x86	The separate 32-bit installer is available when a supported 32-bit client setup needs it. It does not provide a 32-bit SQL Server engine or change the guide's 64-bit loading program.

7. Record the SQL Server address, loading computer, Windows account, SSIS version, execution path and provider in the setup record. For the local setup, keep the same Windows account for the connection tests and later loading commands.

If installation fails

1. Read the first failed setup rule or component in the installation summary. Save the error without passwords.
2. Correct that problem and rerun the affected installer. If the loading-program path is missing, check that Integration Services 2022 was selected, rather than only the database engine or SSMS.
3. Repeat the failed check. Confirm that SQL Server is running and the loading-program path and version are recorded.