29 réponses à ce sujet

[Jeffonl1]

FYI for other users, the (deployment) manifest is something used to install necessary library files in an OS.  As Darth implies, it can be a rather brute force method.

 

For those of you wondering, Darth has installed a newer version of SQL: MSSQL2008R2...  it is fully compatible with win8 (the older 2005 will work on win8 but with some minor issues):  hence his scripts are reporting two Servers.  He has moved the database from MSSQL Server BWDATOOLSET to MSSQL2008.

To use his scripts you must adapter the server name to the server in-use.

 

This is not for the faint of heart

[rosey1579]

Okay. Two things.

1. Stop speaking chinese

2. The toolset just launched

[DarthGizka]

1. Stop speaking chinese

The info I posted may be helpful for other people who want to troubleshoot toolset database problems, because it could save them hours of poking around in the wiki, trawling the SQL server online help and conducting experiments to find out what's what.

Potential troubleshooters will likely be used to firing up SQL Server Management Studio whenever their databases are making creaky noises, but that is usually not an option in a troubleshoot-by-forum-post scenario. That's why I posted the sqlcmd examples. The rest serves to clarify and extend the info found in the wiki.
 

2. The toolset just launched

 
Houston, where's the bloody champagne already! 

[luna1124]

Okay. Two things.

1. Stop speaking chinese

2. The toolset just launched

So, you have it working now??? What did you do differently this time to make it work?

[rosey1579]

The reconfiguring seemed to work... May I have a glass of the bubbly too?

Now I just have to figure out how it works...