Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
dataphile
Yak Posting Veteran
71 Posts |
 Posted - 2003-03-24 : 10:51:28
|
| I have an application server that represents a web server but maintains a persistent database connection across sessions.The clients (think web browser) communicate with the app server via XML (syncronously) and can browse data (first, previous, next, last, insert update delete etc.).Each screen (web page) can potentially contain one recordset/cursor.My question(short version) is:Should I keep the cursor at the application level (as a recordset) or at the database level (SQL: CREATE CURSOR)? |
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2003-03-24 : 22:33:27
|
| Well, if you're using XML then you can't really use EITHER kind of cursor. It makes more sense to just load the XML into a DOM object and then traverse the tree using normal XML methods.SQL Server outputs data in XML format, it does not store or otherwise use XML. Putting the data on the client, then converting it to XML, kinda defeats the purpose of using a recordset at all. It's really one or the other, not some combination of both. It's better to have SQL Server convert the data to XML and store it on the page as an XML data island, you can navigate it to your heart's content using client-side DOM methods. |
 |
|
|
dataphile
Yak Posting Veteran
71 Posts |
Posted - 2003-03-25 : 04:58:02
|
| I understand what you mean. I am not querying XML data though. Please bear with me.<background>The app server connects to the database and executes a query and then converts the Current record in the recordset into XML that is sent to the client. This allows the client to browse a server side recordset without refreshing the presentation layer (HTML). Only the data is refreshed. I do not want to use SQL server's XML directly.</background>My concern is between the application server and the database. With a persistent database connection, do I keep the cursor at the application level in a recordset or in the database in a SQL cursor?...to pass one record at a time to the client ? |
|
|
|
dataphile
Yak Posting Veteran
71 Posts |
Posted - 2003-03-25 : 07:24:20
|
| Got it thanks.I am moving to xforms at the client and moving the cursor to the database. |
|
|
|
|
|
|
client vs. server cursor