Hi Jason
This is a partial solution for my problem, I wonder if I can somehow
specify a flag for each sp. What you do surely will work but imagine if I
have modified released a new version and a small modification in one table
or sp is done, I really don't see it wise to drop all the objects and
recreate them. Only the objects in question should be dropped/recreated or
altered.
I should probably try to find a way to specify versions for each object
alone. An Idea just occurred to me, In think I have to create a system table
that contains all the object names (I know it already exits in all DB
engines) but I'm not sure if I can alter their structure, even if I could I
prefer to have my own table which will have store the version of every
object. I think this will fasten up the process a little bit, because in
this way I don't have to check all the table structures every time I launch
a new version but only those tables that have a new version
If anyone has better suggestions I'd be glad to hear them
Thanks for your help Jason
Vahan
-----Original Message-----
From: [email protected] [mailto:[EMAIL PROTECTED] Behalf
Of Jason Fischer
Sent: Monday, May 09, 2005 12:37 PM
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
a.. To visit your group on the web, go to:
http://groups.yahoo.com/group/delphi-en/
b.. To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
c.. Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
[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/
