No you must close the connection on the reader by using reader.Close(); after you use it. This will close the connection.

Joe

Yes, the connection must be open for reader to read. If you use the overlaod of ExecuteReader that takes a connection string then all you have to do is reader.Close(); and it will close the connection.

If you use the overload that takes a connection, then it is up to you to call connection.Close() after calling reader.Close() since you created the connection yourself.

So I almost always use the connectionstring overload as this is the safest easiest to use, all I have to remember is to close the reader.

The only time to use the overlaod that takes a connection is if you want to use the same connection for several tasks in a row before closing it.

Joe

How are you creating the users? Are they mojoportal SiteUser objects being created in rapid succession or some custom objects?

It might be better to call the data code directly for this run once code and that would use ExecuteNonQuery instead of ExecuteReader. The only thing I can think of if you are using ExecuteReader is must be creating a lot of objects like SiteUser that use reader internally to populate the instance. If any of those are failing to close the reader it can leave the connection open. Other than that maybe there is some slight delay between reader.Close() and the time when the conneciton becomes available again in the connection pool. If it fails at 1000 records maybe let the thread sleep a few seconds every 500 iteration or so to allow a little time for the connection pool to recover resources.

Hope it helps,

Joe