Fusion ECM Dev Env Part One SQL Server Express 2005

January 13, 2009

In this entry we will learn how to get SQL Server Express 2005 downloaded, installed and configured properly for use with Fusion ECM. We will also learn why you must select and download just the right version of the Express Edition to get the most search options.

The disclaimer: This is certainly not the only way to setup your Fusion ECM development environment. Hopefully we will get some opinions and additional information in the comments. Why am I not using Oracle? I could, I use SQL Server for .NET Development a lot as well, so this just happens to fit better for me.

Over the next several blog entries I will be detailing how to setup a Fusion ECM development environment using Apache, Windows Server 2008 and SQL Server Express 2005. There are several spots on the internet where people talk about running on IIS7, but I could not find anyone that has posted this for public knowledge yet.

First, the CORRECT download. Ultimately, the proper version to download is here. Why is this version correct? We select this from the other download options because this one contains Full Text Searching.

Install it. During the installation you will want to uncheck the box that says hide advanced options. Part of those advanced options will ask you for an instance name, make this the default instance instead of a named instance and you'll have an easier time later down the road. You may be prompted that you have successfully satisfied 14 of the 15 prerequisites. If the warning is about your lack of IIS you can skip over that unless you want to run reporting services, which is beyond the scope of this outline.

Finally, the configuration of the installed SQL Server Express 2005 database begins by running Start > All Programs > Microsoft SQL Server 2005 > Configuration Tools > SQL Server Surface Area Configuration. Once you have the UI loaded click the 'Surface Area Configuration for Services and Connections' option.

The trick here is to make sure that under remote connections you have selected 'Use both TCP/IP and Named Pipes' thereby enabling local and remote connections. This will require you to restart the SQL Server windows service.

The next step checks your port configuration. The port will eventually be used in your JDBC connection string. If you selected default instance during installation you're probably already done. To check the port we need to go back to the start menu with Start > All Programs > Microsoft SQL Server 2005 > Configuration Tools > SQL Server Configuration Manager. Expand SQL Server 2005 Network Configuration.

Right click on TCP/IP and then click the IP Addresses Tab. Ensure that the TCP Port entry is set, and in this case since I selected this as my default installation it is set for 1433.

The database is now ready.

© 2020 Jason Stortz (version 20200607-210013)