Invoke-AdoCommand - Support for CommandTimeout?

Topics: Developer Forum
Jun 2, 2010 at 1:39 AM

This is a feature request for future builds -- I use pscx's ado commands pretty heavily in a number of projects, though we've run into some trouble in certain instances where the remote SQL server is on the other end of a slow connection. In these instances using straight system.data.sqlclient code, we just alter the SqlCommand's CommandTimeout property. 

Perhaps a CommandProperties hashtable could be added to Invoke-AdoCommand that would resolve property/value pairs and pass them through to the underlying provider's Command object?

Developer
Jun 2, 2010 at 2:05 AM
Good idea.

On Tue, Jun 1, 2010 at 8:39 PM, genuye <notifications@codeplex.com> wrote:

From: genuye

This is a feature request for future builds -- I use pscx's ado commands pretty heavily in a number of projects, though we've run into some trouble in certain instances where the remote SQL server is on the other end of a slow connection. In these instances using straight system.data.sqlclient code, we just alter the SqlCommand's CommandTimeout property. 

Perhaps a CommandProperties hashtable could be added to Invoke-AdoCommand that would resolve property/value pairs and pass them through to the underlying provider's Command object?

Read the full discussion online.

To add a post to this discussion, reply to this email (Pscx@discussions.codeplex.com)

To start a new discussion for this project, email Pscx@discussions.codeplex.com

You are receiving this email because you subscribed to this discussion on CodePlex. You can unsubscribe or change your settings on codePlex.com.

Please note: Images and attachments will be removed from emails. Any posts to this discussion will also be available online at codeplex.com




--

---
404 signature missing
Developer
Jun 2, 2010 at 6:39 PM
This discussion has been copied to a work item. Click here to go to the work item and continue the discussion.