Installing Oslo SDK and creating an Oslo repository from scratch

Because my machine doesn’t perform well enough when running a Virtual PC image I ventured out to install the Oslo SDK onto my Windows Vista. Turns out to be a worthwhile experience.

Some requirements while trying to install it caught me off-guard:

  • Windows Installer 4.5 to be able to install the next one (SQL Server 2008).
  • SQL Server 2008. I installed the Express version which is a free download.

After preparing your machine, you are ready to install.

  1. Install Oslo SDK
    Download and install the Oslo SDK October 2008 CTP from the Oslo Development Center. Pretty simple. Next, next, Finish. You will notice that the repository could not be installed if you have an Express edition or non-default instance (cheapskate-me installed the Express edition). Not to worry, just read on. Even if you have got a default instance, you might want to create the repository by hand for reason obvious in the next step.
  2. Create the Oslo repository
    Go to the C:Program FilesMicrosoft Repository folder and run the following command:

    CreateRepository.exe /RepositoryAuditing+
      /SchemaPolicy+ /RepositoryName:TestRepository
      /DataFileInitialSize:20MB /DataFileGrowth:10MB
      /LogFileInitialSize:20MB /LogFileGrowth:10MB
      /Verbose+ /SqlServer:.SQLExpress

    Let’s elaborate on some of the command-line options I have specified:

    • Repository auditing is not enabled by default. Consider turning it on straight away. I have no real arguments for doing so, and I am not sure if it can be turned on afterwards (I guess it should be possible). Same goes for Schema policies. AFAIK policies and auditing are only available for full SQL Server installations (as in: not for Express editions).
    • The default initial size of the Repository is a whopping 1GB. I have plenty of hard disk space on my machine, but not that much. How about you?
      Make sure you also change the log file initial size and the growth sizes for both the data and log file. Otherwise you’ll have some 2GB+ less disk space. You have been warned.
    • The SQL server name is critical if you have a named instance or want to install on a remote server. For a local SQL Express it needs to be ‘.SQLExpress’.
    • Verbose: it’s always nice to see what is going on
    • Specify a different name for the repository if you want to have multiple instances running side-by-side or don’t like the default one of ‘Repository’.
  3. Backup the repository
    Perform a backup of the repository database either at this point or later. This will make it lightning fast to restore a repository database in case of a total mess-up on your behalf or the pre-alpha software (I bet it will be the former). There is no good tooling support just yet for removing models from the repository, so a restore from backup is the recommended workaround. You might consider doing the backup after installing the Microsoft models (see next step).
  4. Install the Microsoft models into the repository
    The Oslo SDK has a precompiled image for their Oslo models in it. Check out the “C:Program FilesMicrosoft Repository” folder again and find a model image file called Models.mx. To install this into the repository type:

    mx.exe -i:models.mx -s:.SQLExpress -db:Repository

    I found that this image and one that you compile by hand from the model source code (at “C:Program FilesMicrosoft Oslo SDK 1.0Models”) are not equivalent.
  5. All done
    Yep, you’re ready to go.
Advertisements
This entry was posted in Uncategorized. Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s