Getting the BizTalk SQL Server DB Name

A quick one. How to get the name of the SQL Server that BizTalk is running? A relatively easy way is to get it from the registry. Heres a code sippet that does just that.


string strBtsSvrSubKey =
"Software\\Microsoft\\BizTalk Server\\3.0\\Administration";
string strBtsSqlSvrKey = "MgmtDBServer";
Microsoft.Win32.RegistryKey key = Microsoft.Win32.Registry.LocalMachine.OpenSubKey(strBtsSvrSubKey);
string strBtsSqlSvrName = key.GetValue(strBtsSqlSvrKey).ToString();

Any queries, post a comment.

Comments

Nimbus said…
The me is back. Since you insist that one has to have a query to post a comment, here's mine — How does one write creative comments on a blog without offending the author, who seems to take his geek-writing pretty seriously?

A code snippet explaining the solution is, of course, always appreciated! :)
December 06, 2004 3:17 PM
Anonymous said…
i saw that debate between u and steve on the MS discussion boards about which was better. registry lookup or WMI? so which is it?
December 06, 2004 5:32 PM
Post a Comment

Popular posts from this blog

Using recursion in the In-line XSLT Template type Scripting Functoid

People using In-Line XSLT Templates in their scripting functoids often run into the need for looping, WITHOUT using an <xsl:for-each> . An example in the BizTalk context would be, if you had a comma separated string in the source schema and wanted to tokenize it into multiple destination schema elements. The following XSLT template does that for you. <xsl:template name="TokenizeCommaSepString"> <xsl:param name="stringToTokenize" /> <xsl:param name="destinationElementName" /> <xsl:if test="$stringToTokenize != ''"> <xsl:choose> <xsl:when test="contains($stringToTokenize, ',')=0"> <xsl:element name="{$destinationElementName}"> <xsl:value-of select="$stringToTokenize" /> </xsl:element> </xsl:when> <xsl:otherwise> <xsl:element name="{$destinationElementName}"> <xsl:value-of select="substring-be...
Read more

Sending Messages as FORM Variables with the HTTP Adapter

Image
Here's a quickie. If you want to send a message, as a FORM Variable in a HTTP request, this is what you do: 1) Set the Content Type property of the HTTP send port, to application/x-www-form-urlencoded . 2) Create a custom pipeline and plug-in a Custom Pipeline Component, that pre-pends Variable-Name = in front of the message, and url encode it. e.g: ClaimPacket= 3) Use this pipeline with your HTTP send port, and you are done! Post a comment for a sample. Update : Screen shot of the Content Type property:
Read more