Don't do it! There'll be many users of your application that will happily slap you back into stone age. I'd say about 100 rows should be the limit, that a user can handle.
Provide filters that reduce the number of row to a tolerable level.
Then give them a filter that selects the latest 50 records. Is that relevant at all? What are the main search criteria for the users? What are must haves, what are nice to haves?
You should have some sort of specification. Just dumping all records into a GUI is no solution.
I hope by now you realize you won't get people to design the stuff for you. That's your job as a programmer and also to perform the research required to do whatever solution you come up with.
It seems to me that you want to mimic pagination that you see often in web applications. You want to give the user the opportunity to navigate the huge pile of results you may have, but you display only a limited set of the total result (say - 100 items per "page") as to not bog down the user interface and drive up the resource usage.
Now lets say that you agree with me and that is what you want: what are you going to do? Are you going to ask how to do that, or are you going to google "java swing jtable pagination" ? I hope the latter.
currently I am loading 1000 records initially which is not taking much time and later i load 1000 records every after 2 seconds.
hope this will solve my problem.
And whatever you said about pagination is right i want to same as you said but later for another display. I want to display my records like a PAGE of book .
and also if Page ends with line then next page will continue with the same line. Look will be same as book like we see hard copy.