I wouldn't do one at a time... That would be for pages, not records.
But still. Who scrolls thru pages & pages of data? Except maybe sequential data like this thread. But not rows in a DB. Give the user an interactive Search function and filters that make sense for that type of data. If you build your search well, then the user will find the row he wants within 2 to 4 keystrokes.
Most devs forget that over the life of an app the list will grow to 100K/millions of rows. You are NOT going to use the paging. Trust me.
When developing, you use a few lines or at most a 100 then the paging work ok (still terrible UX though). But in the wild it is a different story.
My advice: don't use it. Do it properly