Hi Vahan, What we have done, is we send an encrypted file with the SP and Triggers in with a version number as part of the file name. When the app runs, it checks the version number of itself against a version number stored in the DB. If the version of the DB is older than the EXE, it will exceute the SP script.
All triggers and SP's are droped and recreated as part of the SP script. Not sure if this will work for you, but at least you don't have to check all sp's and triggers to know if they have changed. Regards, Jason --- In [email protected], Vahan Yoghoudjian <[EMAIL PROTECTED]> wrote: > Hi Group > > I'm using SQL Server... In my application I have hard coded the database > and table definitions, > when we release new versions the application on startup checks the table > definitions and modify the structure in the database in case any changes are > found in the database. That includes creating,modifying and deleting > database objects. > We have implemented this way to have an easy way to update our > softwares. We just sent the .exe to the client and the .exe itself does the > rest of the job... > Now my problem is that I also have stored procedures in these databases, > I can hardcode the stored procedure also and check if it exists already in > the database or not to create it. But if the sp already exists but its > contents are modified, how can I verify that? I'm not sure if scanning all > the sp contents one by one in the database is a good idea, is someone > familiar with any other way? Same applies for triggers also... > > Thanks in advance > Vahan > > > [Non-text portions of this message have been removed] ----------------------------------------------------- Home page: http://groups.yahoo.com/group/delphi-en/ To unsubscribe: [EMAIL PROTECTED] Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/delphi-en/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
