Options
Timeout
Brian Donahue
Posts: 6,590 Bronze 1
Hi René,
At the moment, the timeout value for the databases you've scripted can't
be changed. You can get around the problem by converting the Execution Block
to a string and running the SQL with SqlCommand.ExecuteNonQuery(). That way,
you can construct your very own SqlConnection object with a
ConnectionTimeout property that you can set.
Hope this helps!
Regards,
Brian Donahue
Red Gate Technical Support
"BDE" <informationNOSPAM@bde.de> wrote in message
news:CoeAERp5DHA.1552@server53...
> Hello everyone,
>
> i tried to use sqltoolkit,
>
> i have very much objects in my databases, so
> the resulting sqlskript is very long.
> when i try to start the block with utils.executeblock
> i get (after a while) an timeout. Copying this skript in Query Analyser
then
> it runs very well.
>
> Sorry for my bad english
>
> Regards
> René
>
>
At the moment, the timeout value for the databases you've scripted can't
be changed. You can get around the problem by converting the Execution Block
to a string and running the SQL with SqlCommand.ExecuteNonQuery(). That way,
you can construct your very own SqlConnection object with a
ConnectionTimeout property that you can set.
Hope this helps!
Regards,
Brian Donahue
Red Gate Technical Support
"BDE" <informationNOSPAM@bde.de> wrote in message
news:CoeAERp5DHA.1552@server53...
> Hello everyone,
>
> i tried to use sqltoolkit,
>
> i have very much objects in my databases, so
> the resulting sqlskript is very long.
> when i try to start the block with utils.executeblock
> i get (after a while) an timeout. Copying this skript in Query Analyser
then
> it runs very well.
>
> Sorry for my bad english
>
> Regards
> René
>
>
This discussion has been closed.
