NewsArchive
02-06-2008, 03:40 AM
I have an install, which packages SQL Express with it. However, because of
the size of our application suite, and the potential size of the database if
used multi-user, we recommend a "better version" of MS SQL. To accommodate
this, we have completely twisted up the SQL install script to be one of our
own, prompting whether to install the included SQL express, or a
"customer-purchased" version. If the later, it helps the user find the
setup.exe, and runs it with our switches, setting up our own instance with
the security we need to work.
All this being said, I have run into a problem. PID keys. Currently I am
using a command line install, but I believe an INI install will have the
same problem. If you don't provide a PID key, the install process fails.
However, other than popping a dialog and just asking for it with no
validation seems to be an obvious point of failure.
So, What are the recommendations? What is the best way to handle the PID
key the MS SQL requires during install?
Anyone's help is appreciated!
-Glenn.
the size of our application suite, and the potential size of the database if
used multi-user, we recommend a "better version" of MS SQL. To accommodate
this, we have completely twisted up the SQL install script to be one of our
own, prompting whether to install the included SQL express, or a
"customer-purchased" version. If the later, it helps the user find the
setup.exe, and runs it with our switches, setting up our own instance with
the security we need to work.
All this being said, I have run into a problem. PID keys. Currently I am
using a command line install, but I believe an INI install will have the
same problem. If you don't provide a PID key, the install process fails.
However, other than popping a dialog and just asking for it with no
validation seems to be an obvious point of failure.
So, What are the recommendations? What is the best way to handle the PID
key the MS SQL requires during install?
Anyone's help is appreciated!
-Glenn.