Got the same PC as you, using a Steam installation, and I recently won the battle with the toolset, but I've already half-forgotten the work I did to pull it off (my mind blocking the torment to protect me, no doubt). What I do remember is that, like nezroy said, the SQL 2005 packaged with the Toolset utterly refused to work, and that I needed to install the 2005 Express version from Microsoft's site, along with SQL Server Management Studio Express, to even get started in the right direction. Then I used the Manual Database Installation page combined with sheer guesswork to handle the rest. No idea what's different about the 2008 version. As for some of the things I still recall tripping me up, you absolutely cannot forget that when you install the server manually, you can't use the default database and server links in ConfigureToolset, all that has to be changed around to match the adjustments you make in SQL Studio. For example, my ConfigureToolset has this under Content Database: "Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=bw_dragonage_content;Data Source=.\SQLEXPRESS" instead of the default string, and ".\SQLEXPRESS" for a server name instead of ":\BWDATOOLSET". Basically, change every instance of BWDATOOLSET you find. That little detail messed me up right until the very end. Oh, and you have to make sure every relevant folder has permissions granted, even the empty ones, and that they're in the right places on your installation drive. For example, at the "Backup media" part of the Management Studio tweaking, things might end up pointing to a folder that doesn't exist in the default filepath it attempts to follow, so you have to create it yourself. In my case, I had to put it into Program Files; it kept trying to go into my C drive for no reason I understood. Sorry, that's all I remember, and I'm not sure it even makes sense. May the Maker be with you.