/build/static/layout/Breadcrumb_cap_w.png

How do I configure a transform/.mst for an SQL Server and SQL Server Database?

Still kind of new to packaging, so please be patient.
I am tasked with configuring a transform/.mst (installshield) for an MSI created from a capture. The capture was only files being added to a folder, also created during the capture. The executable needs to connect to the SQL Server and Database. The information provided to me to work with as follows:

SQL Server: Tabquery.prod.xxx.comĀ  (xxx - to represent omitted characters)

Queries SQL Server: tabfusionrms.prod.xxx.com

Is this as simple as adding these as properties to Property Manager in the transform? I am not able to test as the servers are in Production and not available in our test environment.

Thank you in advance!


0 Comments   [ + ] Show comments

Answers (2)

Posted by: vjaneczko 8 years ago
9th Degree Black Belt
0
The easiest way to incorporate database configuration information into an MSI/MST is by exporting the registry keys from a known good machine and adding them.
Posted by: anonymous_9363 8 years ago
Red Belt
0

>exporting the registry keys
That advice assumes that the connection will be via ODBC which may not necessarily be the case.

With nothing in the test environment (I'm wondering, though, what's preventing you from running up a VM, installing WinServer and SQL Server Express in that environment...) you're going to have to take a 'Before' and 'After' snapshot on a Production machine. That's the only way you're going to know what the configuration involves, be that registry, INI or XML file, whatever...

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ