E
Earl
Right now, I have an app with an SQL2k backend that is just getting revved
up. Currently, I fill my datatables with everything that is in the real
database table (I've done a good job of normalizing the database, so the
tables are fairly thin). After fill, I then populate a grid for historical
purposes and use the in-memory datatable to allow the user to
add/update/delete. Everything works well. For the time being.
But what happens when I have 10,000 or even 100,000 records in a particular
table? I surely do not want to create an in-memory datatable with that many
records. While I can probably figure out how to deal with TOP 100 or
whatever for display purposes, I'm curious how others handle this situation
for Update and Delete scenarios? What happens if you are displaying TOP 100
and the record you need is not in there for, let's say, Update -- another
trip to the server to retrieve the record you want to Update -- and another
partially filled table?
up. Currently, I fill my datatables with everything that is in the real
database table (I've done a good job of normalizing the database, so the
tables are fairly thin). After fill, I then populate a grid for historical
purposes and use the in-memory datatable to allow the user to
add/update/delete. Everything works well. For the time being.
But what happens when I have 10,000 or even 100,000 records in a particular
table? I surely do not want to create an in-memory datatable with that many
records. While I can probably figure out how to deal with TOP 100 or
whatever for display purposes, I'm curious how others handle this situation
for Update and Delete scenarios? What happens if you are displaying TOP 100
and the record you need is not in there for, let's say, Update -- another
trip to the server to retrieve the record you want to Update -- and another
partially filled table?