If it's being used in ASP.NET, store it in the Application cache. If it's a WinForms app, store it in a file on the client's machine (being prepared to compute it if this client doesn't have a copy), or possibly make it the result of calling a web service (if you don't want to write to the client computer).
But the people who say it'll be slow to keep it in SQL Server are thinking of doing it over and over and over -- you won't need to do that, will you? (Once you've got it, just keep it in memory, or in the Application cache if using ASP.NET.) To grab it once at startup, having it in your SQL database isn't a bad approach (assuming it's not your only reason to be accessing the database)! At 01:15 PM 8/24/2004, Vitesh Aggarwal, Noida wrote >Thanks Jekke/Amit, > >But I m doing all this to gain performance ...!! >Actually it takes a lot of time to compute that dataset which I wanna store >...thats y I m keeping it in DB, so that its readily available whenever >required... > >The size od this Dataset can easily go more than 10k... >Can u suggest some other approach ?? J. Merrill / Analytical Software Corp =================================== This list is hosted by DevelopMentorŪ http://www.develop.com Some .NET courses you may be interested in: Essential .NET: building applications and components with CSharp August 30 - September 3, in Los Angeles http://www.develop.com/courses/edotnet View archives and manage your subscription(s) at http://discuss.develop.com
