Is there a repository for expressions

Forgive me if there's an obvious answer for this.
I was wondering if there was the facility to save expressions that
you would use in multiple reports. The ones we're looking at
specifically
create a value in a detail line by doing arithmetic on other detail
column values.The simplest way is to write a simple assembly and put the logic there.
Then you reference this assemby from your reports and use a
=myAssembly.myFunction(param1, param2) type syntax in the textbox.
If your assembly only performs calculations or other simple procedures,
you don't have to worry about code access security. There is
docmentation on this in MSDN.
jensisql

Is there a easy way to backup by DTSs?

Hi,

In order to backup by DTS packages, currently I individually open each DTS package in Design mode and then save them as Structured Storage File. Since I have a # of DTS packages and due to the current nature of the work these are changed frequently therefore this backing activity takes time.

Is there a simpler solution via which I canbackup all my DTS packages?

Many TIA.Hi,

have a look here:
http://www.sqldts.com/?242

Carsten|||Hi,

have a look here:
http://www.sqldts.com/?242

Carsten
Thanks. Is this a freeware or a shareware?|||Think it's freeware. But it's mentioned in the license (which is quite short ;-) )|||Aye its freeware "You can use and distribute the software internally within your organisation".
This product works so well, we have an scheduled job which backups 5 server's DTS packages to a central location. :-)

Is there a delay writing to an SQL Database

---

Can someone advise if there is a delay in data being written to the database following a tableadapter.update(datatable) command?

I save transactions which are subjected to the above and then a listview is updated to reflect them.

As I work through all is OK and the transactions appear in view.

I then run a backup through my app using a backup object to do this and this reports all OK

I then close the app and re-open and as as I am in debug the database is empty.

I perform a restore through my app using a restore object and selecting the backup file I created previoulsy which reports all OK

The retore procedure calls application.restart to allow the app to initialise to the restored data.

The problem is quite a bit of my data in missing from the restore as if the last block I did prior to backup never actaully made it to the database?

I also rememeber noting that at times when the update method is performed the actual timestamp on the physical databse is not updated....until I close the app and return to the designer?

So does this mean then prior to performing a backup I have to somehow force the app to ensure it has written all changes to the databse?

Thanks

hi,

very loosely speaking, "updates" (as long as all operations) are always written to both data and log files..

log entries are immediately written in syncronous way, so that transactions can be later committed/rolled back even in case of a system crash... on the other side, physical flush to the database "data" files is performed at "scheduled" time (in async mode to boost underlying OS I/O activity and not to make the database service wait for completation aknowledge), that's to say at checkpoint occurrances...

but even if a crash occurs before the physical data flush to the data files, at next SQL Server start up the data will be recovered/rolled back (depending on completation and commit status of the relative transactions) when every and each database is started up, entering the "redo" and "undo" phases to check what still need to be written to data file(s) (to the actual tables) from the log file(s) analysing all active LSNs (log sequence number) in order to find what need to be serialized.. so, usually, you are not concerned with such a deal in your application if not in case of real disaster and database corruption as, again, even in case of a system crash the database, at next start up, must (and actually "is", if no corruption is on the air) recovered to a consistent state...

so, I'm guessing you are using the User Instance feature provided by SQLExpress..

I'm also guessing you set the "Copy to Ouput directory" property of your database file(s) to "Always" and that you took a backup of your "original" database and not the one you are interested in, that's to say the one you were working with at debug/run time..

is this the case?

regards

|||Hi, thanks for your explanation, this will prove useful.

I found out from another forum that when performing a backup/restore it is better to do it using the release version of the application rather than testing in the IDE!

Once I did this all worked well.

IS Package doesnt ship with password

Hi,
I tried many times checking "Save password" in connection manager editor. But everytime I open the editor again and I see the password field blank.
I took it as normal, and deployed my IS Package, It couldnt run because of login failed for user 'sa'.

How do I force IS to save password on any ProtectionLevel ?

Thanks,
Fahad

Fahad349 wrote:

Hi,
I tried many times checking "Save password" in connection manager editor. But everytime I open the editor again and I see the password field blank.
I took it as normal, and deployed my IS Package, It couldnt run because of login failed for user 'sa'.

How do I force IS to save password on any ProtectionLevel ?

Thanks,
Fahad

You can't. You'll have to set it through dtexec. SSIS doesn't save passwords. There are plenty of threads in this forum on that topic.|||First, /SET option isnt working
I am trying it this way
U sa /P gama /SET "\Package.Connections[TRIMURTY.TMDB.SA].Properties[ConnectionString]";"Data Source=TRIMURTY;User ID=sa;Provider=SQLNCLI.1;Persist Security Info=True;Auto Translate=False;Password=gama"

Second, I have to run this IS Package from another IS Package as well by using Execute Package Task. How would I supply these things on there ?

Please help me
Thanks
Fahad

Phil Brammer wrote:

Fahad349 wrote:

Hi,
I tried many times checking "Save password" in connection manager editor. But everytime I open the editor again and I see the password field blank.
I took it as normal, and deployed my IS Package, It couldnt run because of login failed for user 'sa'.

How do I force IS to save password on any ProtectionLevel ?

Thanks,
Fahad

You can't. You'll have to set it through dtexec. SSIS doesn't save passwords. There are plenty of threads in this forum on that topic.

|||If you're promoting these packages to the MSDB database in SQL Server, have you looked at using ServerStorage for the ProtectionLevel property?|||I have read about ServerStorage, It has nothing to do with storing connections' passwords but storing the Package.|||

Fahad349 wrote:

I have read about ServerStorage, It has nothing to do with storing connections' passwords but storing the Package.

No, not true. it means it relies on SQL Server to match up the assigned user to the SQL server user account.

ServerStorage: "Protects the whole package using SQL Server database roles."|||Here I am not interested in package protection or package security. I am interested in saving password with package. or to avoid this error "login failed for user 'sa'"

ProtectionLevel ServerStorage doesnt let me save the DTS Package in designer.|||

Fahad349 wrote:

Here I am not interested in package protection or package security. I am interested in saving password with package. or to avoid this error "login failed for user 'sa'"

ProtectionLevel ServerStorage doesnt let me save the DTS Package in designer.

Right, but again, you cannot save the password with the package. Can't do it. When you save to the server, you can choose SQL Server role security. Or, try EncryptSensitiveWithPassword. Using that though, you'll have to issue the password everytime the package executes.|||

Phil Brammer wrote:

Right, but again, you cannot save the password with the package. Can't do it. When you save to the server, you can choose SQL Server role security. Or, try EncryptSensitiveWithPassword. Using that though, you'll have to issue the

Ok I will issue the password, but that password will be to execute dts and its separate from passwords in connection manager.
And my understanding with this error message is; the Executable is unable to open child package for executing, not connection manager inside this child has error.|||

Fahad349 wrote:

Phil Brammer wrote:

Right, but again, you cannot save the password with the package. Can't do it. When you save to the server, you can choose SQL Server role security. Or, try EncryptSensitiveWithPassword. Using that though, you'll have to issue the

Ok I will issue the password, but that password will be to execute dts and its separate from passwords in connection manager.
And my understanding with this error message is; the Executable is unable to open child package for executing, not connection manager inside this child has error.

Tough to say... I would think it's the connection managers that's throwing the error.|||

Search this forum for configuration files then use these to "freeze" the password.

Philippe