I have a database called MySessions that holds some volatile information for
web sessions.
This database should be configured for fastest read/write operations.I don't
need to back it up (In a catrastrophic failure I just need to fix the
structure, and the data loss is not important).
Which settings should I set? Which recovery model should I use?
Kyle.SQL Server always operate with full integrity, so there no setting which wil
l reduce integrity of
data and hence potentially increase performance. Simple recovery mode will n
ot reduce amount of work
done for you operations, it will only automatically re-use space in the tran
saction log files
(instead of waiting for you to perform a log backup). The only exception to
this is for
create/rebuild/drop index, SELECT INTO and bulk loading data (under certain
circumstances) which can
go in minimally logged mode if simple recovery mode.
So except for that last exception, the only thing you can do is to work at t
he physical level, like
adventuring the data by using RAID 0 and stuff like that.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Kyle Bush" <kyle@.bush.com> wrote in message news:eqwPB01IGHA.2900@.TK2MSFTNGP14.phx.gbl...[v
bcol=seagreen]
>I have a database called MySessions that holds some volatile information fo
r web sessions.
> This database should be configured for fastest read/write operations.I don
't need to back it up
> (In a catrastrophic failure I just need to fix the structure, and the data
loss is not important).
> Which settings should I set? Which recovery model should I use?
> Kyle.
>[/vbcol]
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment