Issue 11 in tarantino: Enhancement: Ability to specify a timeout for executing queries in databse update

[codesite...@google.com]

Status: New
Owner: ----

New issue 11 by ArturDorochowicz: Enhancement: Ability to specify a timeout
for executing queries in databse update
http://code.google.com/p/tarantino/issues/detail?id=11

Currently the timeout is not explicitly specified and defaults to standard
value of SMO which is 10 minutes. I recently had a scenario where this was
not long enough. I would like to be able to specify this timeout, including
an infinite timeout value.

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

--
You received this message because you are subscribed to the Google Groups "tarantino-developer" group.
To post to this group, send email to tarantino...@googlegroups.com.
To unsubscribe from this group, send email to tarantino-devel...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/tarantino-developer?hl=en.

[codesite...@google.com]

Comment #1 on issue 11 by dinh...@gmail.com: Enhancement: Ability to

specify a timeout for executing queries in databse update
http://code.google.com/p/tarantino/issues/detail?id=11

I have attached a patch (to rev 169) for this problem if you're interested.
What it does is to allow you to name scripts with the "timeout"
or "time-out" keyword followed by the number of seconds and it will execute
the query with the correct
http://msdn.microsoft.com/en-us/library/microsoft.sqlserver.management.common.serverconnection.statementtimeout.aspx
property value.

A timeout of 0 = infinite.

Examples:
1_my_migration_with_timeout_of_3600_seconds.sql
001_my_migration_with_timeout_3600.sql
001_my_migration_with_time-out-3600.sql
001_my_migration_with_infinite_timeout_of_0.sql
001 - my migration with timeout of 3600 seconds.sql

Unit tests are included with the code.

To test, use a migration with the following statement:

-- wait for 30 minutes
WAITFOR DELAY '00:30'

And name the file: 1-my_test_with_timeout_of_60_seconds.sql

Hint: you just need to recompile Tarantino.DatabaseManager.Core - actually
I never managed to rebuild the solution properly!

-- Dinh Doan Van Bien

Attachments:
tanrantino_statement_timeout_dvb_2001-08-12.patch 10.7 KB

[codesite...@google.com]

Comment #2 on issue 11 by hzacchi: Enhancement: Ability to specify a

timeout for executing queries in databse update
http://code.google.com/p/tarantino/issues/detail?id=11

Nice one. Thanks Dinh for this patch.