StrataFrame Forum » StrataFrame Database Deployment Toolkit » Database Deployment Toolkit (How do I?) » DDT automaticly created stored procedures with wrong naming

DDT automaticly created stored procedures with wrong naming

Philipp Guntermann — Wed, 30 Jul 2008 09:37:13 GMT

when i add the localization deployment packages to the ddt through the "Create packages using the deployment package wizard" function, it creates the stored procedures wrong.

it adds them with names "dbo." instead of "dbo.MessageItems_Insert" and "dbo.MessageLanguages_Insert"

as shown here in the stored procedures view on the ddt:

i tried deleting the tables in the ddt and from the database and re-adding the localization deployment packages through the wizard, but he does it again :)

any idea ?

RE: DDT automaticly created stored procedures with wrong naming

Trent L. Taylor — Wed, 30 Jul 2008 09:37:13 GMT

[quote]how much of a performance boost are we talking here ?[/quote]

This can depend on a number of factors, especially on whether you intend to localize labels, etc. The more you localize, then the more of a performance boost you will gain. It is embedded within the EXE so no trips to the server are required. The embedded option will be 100% instantaioneous and not impact load performance. If you are pulling from SQL Server, then you can experience a load delay as a trip to the server will be made for each request (until it has been loaded once then it is cached during the run).

So the performance boost is extremely significant and if you intend on localizing every facet of your application, you would be well advised to embed your localization files. If you are only going to pull messages, then it will not be that big of a deal.

RE: DDT automaticly created stored procedures with wrong naming

Philipp Guntermann — Wed, 30 Jul 2008 09:21:20 GMT

[quote][b]Ivan George Borges (07/29/2008)[/b][hr]Hey Philipp.

You probably have a good reaoson to add the Message and Localization tables into your Database, but if not, have a look at the help file under "Using Embedded XML Files", which is the recommended way, and will probably give your application a performance boost.

Cheers.[/quote]

hi Ivan,

how much of a performance boost are we talking here ? there a few reasons why i'd want the localization inside the database rather than using the xml approach, however if it raises a serious slowdown (which i havent seen indications for yet) i might get my head around it and find some solutions for the problems that arise when using xml based localization with this application.

thanks !

RE: DDT automaticly created stored procedures with wrong naming

Ivan George Borges — Tue, 29 Jul 2008 09:53:12 GMT

Hey Philipp.

Cheers.

RE: DDT automaticly created stored procedures with wrong naming

Philipp Guntermann — Tue, 29 Jul 2008 09:02:23 GMT

ok thanks.

RE: DDT automaticly created stored procedures with wrong naming

Trent L. Taylor — Tue, 29 Jul 2008 08:59:38 GMT

If you will search the forum you will see that this is already a known issue and you can see that there is an easy work around. Just right-click the MessageItems and MessageLanguages tables, go to properties, and just clear out the INSERT and UPDATE sprocs, uncheck the items, then re-check them and it will correct the issue.