Creating automated install of Client Tools

  • I built an application around an MSDE database and am looking fo a way to install the client tools (management console, etc...) without having to prompt the user for anything (blind install).

    Also, installing the MSDE is simple, but restoring from a backup of the database into the new install is not so straightforward (all automated if possible). Should I just attach the database? How about creating the specific user required for security?

    What tools do I need in order to accomplish this? How do I create/modify ini files to do this? Am I way off base here? Is ther any documentation on how to do something like this?

    FYI: I am using the Inno Setup Compiler (it's free and this is an internal application, not for distribution).

    Thanks in advance,

    RR

  • Richard,

    I built an application around an MSDE database and am looking fo a way to install the client tools (management console, etc...) without having to prompt the user for anything (blind install).

    Are you familiair with the SUS server pricipal??  No.... ask you Domain Admin group.

    In a nutshell; When starting up you client pc and loging onto you DNS server the Client pc will be checked and if settings are not appropriate (or missing) it will install automaticly.

    Also, installing the MSDE is simple, but restoring from a backup of the database into the new install is not so straightforward (all automated if possible). Should I just attach the database? How about creating the specific user required for security?

    If I read this I think you want to transfer a database to the client...right? Wrong...You'd better configure the MSDE on the client ( register the database ) and contact to SQL server.

    If you excist doing so youd better use the backup and restore facility or use DTS packages to transfer.

    Just a thought on this......succes. 

    GKramer

    The Netherlands

  • Guus, thanks for the reply. I think I found a solution to the problem with one exception, but I have a work around for that. What I did:

    1. I exported the data structure of the database into an sql file

    2. I automated the install of the MSDE data base with the installer

    3. After installation, I started the SQL Manager and started the database

    4. Running the command OSQL /E /i "file.sql" created the database on the new server.

    Since I am not concerned about copying data (it will automatically synchronize with the enterprise server anyway), initializing the structure and users was sufficient.

    What I really was trying to do but cannot is start SQL in the application setup after the SQL server was installed so the OSQL command could be run automatically. I never found a way to do this.

    Oh well, 1 manual step is better than forcing the user to do DTS or Restore functions. I really do not want the user to have access to any of these functions. I (or the IT dept) will do any and all maintenance to the remote locations database's.

    Thanks for the reply!!!

  • Richard,

    I do not know the exact reason you have to copy your data to a client but have you ever thought about replication or logshipping???

    Guus

  • In a nutshell...

    This application is designed to collect data at remote locations, display the data on a production monitor, send the data to an enterprise server for management access via a web portal. The web page is used to manage the remote location operation (what to produce, on what machine, when, etc...). All of this data needs to be synchronized to the local machine. Why? The local machine cannot be solely dependant on the WAN being up all the time. As anyone in IT knows, WAN's drop once in a while and the local app will use it's internal database solely until the WAN is restored, at which time all data is pushed to the Enterprise server. Hence the use of a local database to store/forward data.

     

     

  • Richard,

    This application is designed to collect data at remote locations...

    This sounds like a transactional replication ( pull mechanism )

    send the data to an enterprise server for management....

    Why not build view on it or use OLAP for this ( it frees your actual data source from being used by heavy user traffic (perfomance) )

    reading on... WAN's drop once in a while ....

    Probably a merg replication ( does the same but has te capability to lose contact ).

    I'm not suggesting you have to rebuild your systems but this is a thing I encounter very often examin database environments...When building such an environment most of the time the knowledge is not at maximun level ( designers do not know all posibilities available ) and this often causes very strange situations and workarounds. Somethings can be very much simplified if.....

    Just another thought on this...

    If you want to discuss you situation please keep in contact. As a database designer / architect i'm have an open view and probably can advise you on almost every posible database question .( not only designing but on the RDBMS, as the database motor, as well ).

    GKramer

    The Netherlands

      

     

  • I really appreciate the support. This is my first really BIG project and I tried to think of all possibilities and solutions. Unfortunatly, being a 1 man shop with very limited support network in the community, it is often hard to do everything correctly the first time. I am planning on rebuilding this application for V2.0 later next year when more time presents itself. At that time, I will take your options into consideration.

    Learning by brute force is good, sometimes(LOL ;-&gt!!

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply