Disconnected Recordsets - Where are they Stored

Question

Post reply

Disconnected Recordsets - Where are they Stored

SeanBarberPro

SSC Journeyman

Points: 98
More actions
January 7, 2011 at 3:59 pm

#388582

Hello,
I have a question about Disconnected Recordsets that i havent been able to find much information on.
When the disconnected record set is created on a SQL server where is it stored till it is delivered to the client.
page file or memory, Or a combonation of Both.
Im getting an out of memory error on a large disconnected Recordset.
Thanks
Forum Etiquette: How to post Reporting Services problems

[/url]

Forum Etiquette: How to post data/code on a forum to get the best help - by Jeff Moden
[/url]

How to Post Performance Problems - by Gail Shaw
[/url]

Evil Kraig F SSC Guru Points: 100851 More actions · Answer 1

Sean,

Can you be more specific as to what you mean by a Disconnected Recordset?

The only thing I could find on it is from a programmatical standpoint where recordsets/datasets aren't used in conjunction with a database and are populated via automation.

IE: http://msdn.microsoft.com/en-us/library/Aa260348

I couldn't find anything with this concept in relation to SQL Server... can you please extrapolate?

- Craig Farrell

Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.

For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA

SeanBarberPro SSC Journeyman Points: 98 More actions · Answer 2

This artical explains them better then I can.

http://www.devguru.com/features/tutorials/DisconnectedRecordsets/tutDisconnRS.asp

Evil Kraig F SSC Guru Points: 100851 More actions · Answer 3

Okay, so, basically same thing.

For those following along, a pertinent quote from the article:

These are, as the name suggests, Recordsets that have been disconnected from the data source, thus allowing the user to work off-line and move freely between records. If a Recordset is created with write permission, the user can also alter and delete records, or add new ones. These changes will be cached locally and not affect the main database. Later a connection can be re-established to the database, which can then be updated with the changes. One thing to bear in mind, however, is the possibility of conflict if one person alters a record while someone else is working with the same record off-line.

These are stored at the RAM level. Anything stored in RAM can be stored to the swapfile (pagefile), unless other restrictions are in play.

The idea is that the user doesn't need to hold a spid open to the DB to work within the recordset, amongst a few other things... think offline merge replication issues when this is performed.

I'm not entirely sure if we can help you further here, though you might find a few ADO programmers around, this is a SQL Server forum. This is primarily a programming error in a different language and environment.

- Craig Farrell

Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.

For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA

mister.magoo SSC-Forever Points: 47174 More actions · Answer 4

SeanBarberPro (1/7/2011)
Hello,
I have a question about Disconnected Recordsets that i havent been able to find much information on.
When the disconnected record set is created on a SQL server where is it stored till it is delivered to the client.
page file or memory, Or a combonation of Both.
Im getting an out of memory error on a large disconnected Recordset.
Thanks

Disconnected recordsets are by definition held on the client in RAM/Page File dependent entirely upon available RAM and Recordset size.

The data is delivered to the client before the client disconnects from the server.

MM

select geometry::STGeomFromWKB(0x0106000000020000000103000000010000000B0000001000000000000840000000000000003DD8CCCCCCCCCC0840000000000000003DD8CCCCCCCCCC08408014AE47E17AFC3F040000000000104000CDCCCCCCCCEC3F9C999999999913408014AE47E17AFC3F9C99999999991340000000000000003D0000000000001440000000000000003D000000000000144000000000000000400400000000001040000000000000F03F100000000000084000000000000000401000000000000840000000000000003D0103000000010000000B000000000000000000143D000000000000003D009E99999999B93F000000000000003D009E99999999B93F8014AE47E17AFC3F400000000000F03F00CDCCCCCCCCEC3FA06666666666FE3F8014AE47E17AFC3FA06666666666FE3F000000000000003D1800000000000040000000000000003D18000000000000400000000000000040400000000000F03F000000000000F03F000000000000143D0000000000000040000000000000143D000000000000003D, 0);