In order to install BizTalk Server 2010 at all, we need some kind of SQL Database. I haven’t personally tried any other than SQL Server 2008 R2 in its Full Enterprise edition (thanks to MSDN). Now we’re not going to make any exception to the rule: the more expensive the better and once again we’re going to use SQL Server Enterprise. Of course it’s free and available for download fully functional trial version. Totally enough for our tutorial and BizTalk party.
We download the file from Microsoft and proceed with the installation. Not actually interesting it’s worth to synchronize all the settings so that we can be sure, that everything works as expected.
We extract temporary installation files where convenient. We have to be patient as the whole process can be a little time-consuming. Kaffeepause!
Once it’s finally over, we look for the most convincing file, to start the installation. The one shown below should to the trick.
Again that some time your time…
We’re installing our BizTalk environment from the scratch, so there isn’t any other instance of SQL Server 2008 R2. There can, and after installing Visual Studio 2010 Ultimate, definitely is already installed an instance of SQL Server Express 2008. But that should not be a problem now.
We simply chose Installation from the menu on the left and then New installation or add features to an existing installation.
Surprisingly… we are asked to wait again. If we’re lucky enough we see in a few seconds a window shown below.
The curious reader can of course take a look at details using Show details, but our philosophy for most of the installations that are yet to come is: achieve as much as possible, doing as least as possible. So.. we click OK.
In the next step we’re asked to chose our license type. We simply chose Evaluation (already selected) and click OK.
We accept, what we’ve just read (yeah, right!). Those willing to share their usage info with Microsoft, select apart from I accept license terms also the option Send feature usage to Microsoft. And what? Next.
Nothing left to click but Install. And as we’re kindly asked to restart our computer, having actually no other choice, we click OK.
To my surprise, after clicking OK no restart happened. The installation process went forward showing another summary.
We can simply ignore Windows Firewall warning as we’re not planning to access our SQL Server from the outside world. Then we click Next.
Options in the next dialog we leave unchanged, deciding to Install SQL Server Database Engine Services and all the goods that come in the bundle. We confirm again by clicking Next.
When in the next dialog we chose anything other than Select All we are really likely to be back here again as our SQL Server will be missing any of these magical functions. What’s even more interesting: error messages when any of the features are missing aren’t necessarily always straightforward and that we should install that and that. In most cases we are left with an ErrorCode to google for. So we choose all and confirm clicking Next.
Another test passed, so Next.
Those planning to name the database instance after a cat or a dog should feel free to do so. But what I really recommend is to select Default instance and confirm clicking Next.
Having no other choice we confirm disk space requirements and proceed forward using Next.
In the next step we are asked to bind user accounts with each of the services that will be installed. The easiest and preferred way is to create a new account named for example SQLSERVER. Let’s do this.
We choose one of the simplest passwords, that meet the default system requirements: P@ssw0rd. This is not advised to do so in a production environment, but for our test configuration that definitely enough. We chose to disable password change and allow the password to last forever. We go back to the installation and fill fields so that they match the configuration shown below.
In the next step we make further security decisions.
This time we chose to use Mixed authentication mode providing our standard, super secure password P@ssw0rd. We also chose to Add current user to the group of SQL Server administrators. After that, simply Next.
We chose to promote our current user to the Analysis Services administrator too.
We’re not planning to user SharePoint, although me and my friend Kacper Oko have already succeeded to integrate BizTalk, SharePoint and Workflow Foundation together. We get there with our tutorial some day. I promise. For now the option selected by default is enough and we go forward clicking Next.
This time let’s make Microsoft aware of the bugs we’re going to encounter.
Let’s make it happen… Install. And we have a lot of time to make ourselves a cup of tea or coffee.
We did it. OK & Close. Let’s make a restart and after that we will install BizTalk Server 2010. All that and even more in Part1.4. That’s all folks!