January 22, 2006 at 10:14 am
ok thanks for all replies, i'll start y research by finding a way to tune my sampled database , so any idea on how can i organize my ideas and my research topics what should i start first, from the begining i take a profile and monitor the transactions on the database a whole day and then organize the most long transaction that could affect the performance. so what is next
thankz
Hoodi
January 23, 2006 at 2:08 am
You should also try taking a look at the queries that run most often, even if they are already quite fast.
Tuning the long running queries is fine, but you can often get better performance as a whole by tuning the fast but often run ones too.
December 21, 2006 at 2:19 pm
As always, this site is a good place to look for answers. A group I have been working with asked the same question. Can SQL Server 2000 run a DB completely in RAM? Can 2005? My gut reaction was definitely no in 2000, probably not in 2005. Looks like the Gurus on this site agree.
The reason I had was that SQL Server was built to assure data integrity. That is why it is built with a data file and a log file and has different security models to choose from.
As far as having a read only DB in memory. That is not a DB, it is a copy of a DB. Which by the way C# is designed to do, however C# can also build a full fledged DB with read/write capabilities built into it with or without DBMS/file backup.
Viewing 3 posts - 16 through 17 (of 17 total)
You must be logged in to reply to this topic. Login to reply