Assume a heavy transaction environment.
Let's say we have the same database model,
same hardware, file usage, type of data, queries etc. on two servers.
Server A is configured with a RAID 5 on all the data disks (9 of them),
and Server B is configured with RAID 5 on the data disks (5 of them) but
transaction log and tempdb is separated to its own mirrored disks (4 of
them - 2 each).
Which SQL server will run faster in terms of query response time AND write
performance? Database in Server A or Server B?Assumimng disc io is the limiting factor then I would say B would be =most likely to outperform A. But even better would be lose the raid 5 =and use 0+1 on 4 discs. or possibly on 6 and lose the separation of =tempdb. Of course this will lose you some space over the raid 5, but =will perform better. Hardware raid vs S/W will alo make a difference. =How much separating tempdb gives you totally depends on the number of =queries generating large temporary results.
Opinions are likely to vary a lot and you haven't given much info to go =on.
Mike John
"Rick" <bob@.bob.net> wrote in message =news:3f858779$0$103$8f4e7992@.newsreader.goldengate.net...
> Assume a heavy transaction environment.
> > Let's say we have the same database model,
> same hardware, file usage, type of data, queries etc. on two servers.
> Server A is configured with a RAID 5 on all the data disks (9 of =them),
> and Server B is configured with RAID 5 on the data disks (5 of them) =but
> transaction log and tempdb is separated to its own mirrored disks (4 =of
> them - 2 each).
> > Which SQL server will run faster in terms of query response time AND =write
> performance? Database in Server A or Server B?
> >|||I completely agree with Mike John's remark to drop RAID5 completely,
certainly for a 'heavy transaction environment' as you describe. Check out
this link for some reasons why
http://www.miracleas.dk/BAARF/BAARF2.html
(OK it's Oracle/Unix, but it is as tru for the SQLServer/Win world too..)
"Mike John" <Mike.John@.knowledgepool.com> wrote in message
news:uRds7fpjDHA.2676@.TK2MSFTNGP11.phx.gbl...
Assumimng disc io is the limiting factor then I would say B would be most
likely to outperform A. But even better would be lose the raid 5 and use 0+1
on 4 discs. or possibly on 6 and lose the separation of tempdb. Of course
this will lose you some space over the raid 5, but will perform better.
Hardware raid vs S/W will alo make a difference. How much separating tempdb
gives you totally depends on the number of queries generating large
temporary results.
Opinions are likely to vary a lot and you haven't given much info to go on.
Mike John
"Rick" <bob@.bob.net> wrote in message
news:3f858779$0$103$8f4e7992@.newsreader.goldengate.net...
> Assume a heavy transaction environment.
> Let's say we have the same database model,
> same hardware, file usage, type of data, queries etc. on two servers.
> Server A is configured with a RAID 5 on all the data disks (9 of them),
> and Server B is configured with RAID 5 on the data disks (5 of them) but
> transaction log and tempdb is separated to its own mirrored disks (4 of
> them - 2 each).
> Which SQL server will run faster in terms of query response time AND write
> performance? Database in Server A or Server B?
>|||On Thu, 9 Oct 2003 11:06:17 -0500, "Rick" <bob@.bob.net> wrote:
>Assume a heavy transaction environment.
> Let's say we have the same database model,
>same hardware, file usage, type of data, queries etc. on two servers.
>Server A is configured with a RAID 5 on all the data disks (9 of them),
>and Server B is configured with RAID 5 on the data disks (5 of them) but
>transaction log and tempdb is separated to its own mirrored disks (4 of
>them - 2 each).
>Which SQL server will run faster in terms of query response time AND write
>performance? Database in Server A or Server B?
Well, like the other guys said, one would probably anticipate B
running a bit faster, but it's also going to depend on how much data
is cached, that is, on RAM size, and just how heavily tempdb gets
used, and for that matter, how heavily the log gets used. If it were
100% simple queries, A might even win, for a more usual mix of 90%
simple queries, 5% complex queries, and 5% highly localized updates,
you're probably close to the break-even point, assuming you're not
running short of disk IO bandwidth or CPU in either case A or case B.
J.
Showing posts with label usage. Show all posts
Showing posts with label usage. Show all posts
Wednesday, March 7, 2012
Sunday, February 19, 2012
benefits of full recovery**
Hi
What's the benefit usage to select Full recovery model for a database?
I know it's better to select simple mode for developement and test
enviroment.
But I don't know excatly how can the full recovery model be usefull for
critical enviroment?
Can any body give me an example?
Thanks alot
Maryam,
Here is a nice article:
http://insight.zdnet.co.uk/software/...4171-1,00.htm.
Dejan Sarka, SQL Server MVP
Associate Mentor
www.SolidQualityLearning.com
"maryam rezvani" <rezvani@.parskhazar.net> wrote in message
news:uWJq1njwEHA.3824@.TK2MSFTNGP15.phx.gbl...
> Hi
> What's the benefit usage to select Full recovery model for a database?
> I know it's better to select simple mode for developement and test
> enviroment.
> But I don't know excatly how can the full recovery model be usefull for
> critical enviroment?
> Can any body give me an example?
> Thanks alot
>
|||maryam rezvani wrote:
> Hi
> What's the benefit usage to select Full recovery model for a database?
> I know it's better to select simple mode for developement and test
> enviroment.
> But I don't know excatly how can the full recovery model be usefull
> for critical enviroment?
> Can any body give me an example?
> Thanks alot
short:
if your DB is in full recovery model, you will have to backup the log, if
you can several times/day. In case of a restore, you probably will not lose
any data, and you can recovery to the point in time (useful if someone
deletes something or some other human error)
long:
see BooksOnLine (mssql help)
|||Hi
By using 'FULL recovery' mode you will be able to restore your database at
point time
For example , you do a full backup on sunday night and every hour a log file
backup during the work day ,so on tuesday at 11 AM the database is crashed
..If you have the database in 'SIMPLE recovery' you will be able to get the
database back only from last backup (sunday night) ,that means you lost the
data of monday,tuesday . However , if you have 'FULL recovery' you have to
restore the last database backup and the apply all LOG backups till 11AM
(see more details in the BOL)
Another important point is
Let say you do a FULL backup database every sunday night and every hour a
LOG file backup. Now, you lost the FULL database backup of the second week
and the database is get corrupted now. So what would you do, you are about
to lost the data of two weeks ( if you do only FULL backup database (SIMPLE
recovery) ) ,but in that case you restore the last full backup (two weeks
ago) and the apply all LOG files you perfom till the corruption. You will
lost nothing because LOG file backup contains all info since last LOG file
backup.
"maryam rezvani" <rezvani@.parskhazar.net> wrote in message
news:uWJq1njwEHA.3824@.TK2MSFTNGP15.phx.gbl...
> Hi
> What's the benefit usage to select Full recovery model for a database?
> I know it's better to select simple mode for developement and test
> enviroment.
> But I don't know excatly how can the full recovery model be usefull for
> critical enviroment?
> Can any body give me an example?
> Thanks alot
>
|||Thanks
Do you mean that if I found that some false insertion happenning to a
special table
in 9:00 am and my db is in full recovery model so I can restore my db to the
point
exaclty before the false insertion through the log file?
but if I set my db to simple mode have to restore the previous backup
related to the day before(cause I back up my db every night)?
"Zarko Jovanovic" <mind_less_NOSPAM_@.bigfoot.com> wrote in message
news:1099553502.722414@.internet.fina.hr...
> maryam rezvani wrote:
> short:
> if your DB is in full recovery model, you will have to backup the log, if
> you can several times/day. In case of a restore, you probably will not
lose
> any data, and you can recovery to the point in time (useful if someone
> deletes something or some other human error)
> long:
> see BooksOnLine (mssql help)
>
|||Correct. But for the first scenario, you also need to perform regular transaction log backups. When
you restore a transaction log backup, you can stop at a certain point in time.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"maryam rezvani" <rezvani@.parskhazar.net> wrote in message
news:egP72OkwEHA.4004@.tk2msftngp13.phx.gbl...
> Thanks
> Do you mean that if I found that some false insertion happenning to a
> special table
> in 9:00 am and my db is in full recovery model so I can restore my db to the
> point
> exaclty before the false insertion through the log file?
> but if I set my db to simple mode have to restore the previous backup
> related to the day before(cause I back up my db every night)?
> "Zarko Jovanovic" <mind_less_NOSPAM_@.bigfoot.com> wrote in message
> news:1099553502.722414@.internet.fina.hr...
> lose
>
What's the benefit usage to select Full recovery model for a database?
I know it's better to select simple mode for developement and test
enviroment.
But I don't know excatly how can the full recovery model be usefull for
critical enviroment?
Can any body give me an example?
Thanks alot
Maryam,
Here is a nice article:
http://insight.zdnet.co.uk/software/...4171-1,00.htm.
Dejan Sarka, SQL Server MVP
Associate Mentor
www.SolidQualityLearning.com
"maryam rezvani" <rezvani@.parskhazar.net> wrote in message
news:uWJq1njwEHA.3824@.TK2MSFTNGP15.phx.gbl...
> Hi
> What's the benefit usage to select Full recovery model for a database?
> I know it's better to select simple mode for developement and test
> enviroment.
> But I don't know excatly how can the full recovery model be usefull for
> critical enviroment?
> Can any body give me an example?
> Thanks alot
>
|||maryam rezvani wrote:
> Hi
> What's the benefit usage to select Full recovery model for a database?
> I know it's better to select simple mode for developement and test
> enviroment.
> But I don't know excatly how can the full recovery model be usefull
> for critical enviroment?
> Can any body give me an example?
> Thanks alot
short:
if your DB is in full recovery model, you will have to backup the log, if
you can several times/day. In case of a restore, you probably will not lose
any data, and you can recovery to the point in time (useful if someone
deletes something or some other human error)
long:
see BooksOnLine (mssql help)
|||Hi
By using 'FULL recovery' mode you will be able to restore your database at
point time
For example , you do a full backup on sunday night and every hour a log file
backup during the work day ,so on tuesday at 11 AM the database is crashed
..If you have the database in 'SIMPLE recovery' you will be able to get the
database back only from last backup (sunday night) ,that means you lost the
data of monday,tuesday . However , if you have 'FULL recovery' you have to
restore the last database backup and the apply all LOG backups till 11AM
(see more details in the BOL)
Another important point is
Let say you do a FULL backup database every sunday night and every hour a
LOG file backup. Now, you lost the FULL database backup of the second week
and the database is get corrupted now. So what would you do, you are about
to lost the data of two weeks ( if you do only FULL backup database (SIMPLE
recovery) ) ,but in that case you restore the last full backup (two weeks
ago) and the apply all LOG files you perfom till the corruption. You will
lost nothing because LOG file backup contains all info since last LOG file
backup.
"maryam rezvani" <rezvani@.parskhazar.net> wrote in message
news:uWJq1njwEHA.3824@.TK2MSFTNGP15.phx.gbl...
> Hi
> What's the benefit usage to select Full recovery model for a database?
> I know it's better to select simple mode for developement and test
> enviroment.
> But I don't know excatly how can the full recovery model be usefull for
> critical enviroment?
> Can any body give me an example?
> Thanks alot
>
|||Thanks
Do you mean that if I found that some false insertion happenning to a
special table
in 9:00 am and my db is in full recovery model so I can restore my db to the
point
exaclty before the false insertion through the log file?
but if I set my db to simple mode have to restore the previous backup
related to the day before(cause I back up my db every night)?
"Zarko Jovanovic" <mind_less_NOSPAM_@.bigfoot.com> wrote in message
news:1099553502.722414@.internet.fina.hr...
> maryam rezvani wrote:
> short:
> if your DB is in full recovery model, you will have to backup the log, if
> you can several times/day. In case of a restore, you probably will not
lose
> any data, and you can recovery to the point in time (useful if someone
> deletes something or some other human error)
> long:
> see BooksOnLine (mssql help)
>
|||Correct. But for the first scenario, you also need to perform regular transaction log backups. When
you restore a transaction log backup, you can stop at a certain point in time.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"maryam rezvani" <rezvani@.parskhazar.net> wrote in message
news:egP72OkwEHA.4004@.tk2msftngp13.phx.gbl...
> Thanks
> Do you mean that if I found that some false insertion happenning to a
> special table
> in 9:00 am and my db is in full recovery model so I can restore my db to the
> point
> exaclty before the false insertion through the log file?
> but if I set my db to simple mode have to restore the previous backup
> related to the day before(cause I back up my db every night)?
> "Zarko Jovanovic" <mind_less_NOSPAM_@.bigfoot.com> wrote in message
> news:1099553502.722414@.internet.fina.hr...
> lose
>
benefits of full recovery**
Hi
What's the benefit usage to select Full recovery model for a database?
I know it's better to select simple mode for developement and test
enviroment.
But I don't know excatly how can the full recovery model be usefull for
critical enviroment?
Can any body give me an example?
Thanks alotMaryam,
Here is a nice article:
http://insight.zdnet.co.uk/software...34171-1,00.htm.
Dejan Sarka, SQL Server MVP
Associate Mentor
www.SolidQualityLearning.com
"maryam rezvani" <rezvani@.parskhazar.net> wrote in message
news:uWJq1njwEHA.3824@.TK2MSFTNGP15.phx.gbl...
> Hi
> What's the benefit usage to select Full recovery model for a database?
> I know it's better to select simple mode for developement and test
> enviroment.
> But I don't know excatly how can the full recovery model be usefull for
> critical enviroment?
> Can any body give me an example?
> Thanks alot
>|||maryam rezvani wrote:
> Hi
> What's the benefit usage to select Full recovery model for a database?
> I know it's better to select simple mode for developement and test
> enviroment.
> But I don't know excatly how can the full recovery model be usefull
> for critical enviroment?
> Can any body give me an example?
> Thanks alot
short:
if your DB is in full recovery model, you will have to backup the log, if
you can several times/day. In case of a restore, you probably will not lose
any data, and you can recovery to the point in time (useful if someone
deletes something or some other human error)
long:
see BooksOnLine (mssql help)|||Hi
By using 'FULL recovery' mode you will be able to restore your database at
point time
For example , you do a full backup on sunday night and every hour a log file
backup during the work day ,so on tuesday at 11 AM the database is crashed
.If you have the database in 'SIMPLE recovery' you will be able to get the
database back only from last backup (sunday night) ,that means you lost the
data of monday,tuesday . However , if you have 'FULL recovery' you have to
restore the last database backup and the apply all LOG backups till 11AM
(see more details in the BOL)
Another important point is
Let say you do a FULL backup database every sunday night and every hour a
LOG file backup. Now, you lost the FULL database backup of the second week
and the database is get corrupted now. So what would you do, you are about
to lost the data of two weeks ( if you do only FULL backup database (SIMPLE
recovery) ) ,but in that case you restore the last full backup (two weeks
ago) and the apply all LOG files you perfom till the corruption. You will
lost nothing because LOG file backup contains all info since last LOG file
backup.
"maryam rezvani" <rezvani@.parskhazar.net> wrote in message
news:uWJq1njwEHA.3824@.TK2MSFTNGP15.phx.gbl...
> Hi
> What's the benefit usage to select Full recovery model for a database?
> I know it's better to select simple mode for developement and test
> enviroment.
> But I don't know excatly how can the full recovery model be usefull for
> critical enviroment?
> Can any body give me an example?
> Thanks alot
>|||Thanks
Do you mean that if I found that some false insertion happenning to a
special table
in 9:00 am and my db is in full recovery model so I can restore my db to the
point
exaclty before the false insertion through the log file?
but if I set my db to simple mode have to restore the previous backup
related to the day before(cause I back up my db every night)?
"Zarko Jovanovic" <mind_less_NOSPAM_@.bigfoot.com> wrote in message
news:1099553502.722414@.internet.fina.hr...
> maryam rezvani wrote:
> short:
> if your DB is in full recovery model, you will have to backup the log, if
> you can several times/day. In case of a restore, you probably will not
lose
> any data, and you can recovery to the point in time (useful if someone
> deletes something or some other human error)
> long:
> see BooksOnLine (mssql help)
>|||Correct. But for the first scenario, you also need to perform regular transa
ction log backups. When
you restore a transaction log backup, you can stop at a certain point in tim
e.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"maryam rezvani" <rezvani@.parskhazar.net> wrote in message
news:egP72OkwEHA.4004@.tk2msftngp13.phx.gbl...
> Thanks
> Do you mean that if I found that some false insertion happenning to a
> special table
> in 9:00 am and my db is in full recovery model so I can restore my db to t
he
> point
> exaclty before the false insertion through the log file?
> but if I set my db to simple mode have to restore the previous backup
> related to the day before(cause I back up my db every night)?
> "Zarko Jovanovic" <mind_less_NOSPAM_@.bigfoot.com> wrote in message
> news:1099553502.722414@.internet.fina.hr...
> lose
>
What's the benefit usage to select Full recovery model for a database?
I know it's better to select simple mode for developement and test
enviroment.
But I don't know excatly how can the full recovery model be usefull for
critical enviroment?
Can any body give me an example?
Thanks alotMaryam,
Here is a nice article:
http://insight.zdnet.co.uk/software...34171-1,00.htm.
Dejan Sarka, SQL Server MVP
Associate Mentor
www.SolidQualityLearning.com
"maryam rezvani" <rezvani@.parskhazar.net> wrote in message
news:uWJq1njwEHA.3824@.TK2MSFTNGP15.phx.gbl...
> Hi
> What's the benefit usage to select Full recovery model for a database?
> I know it's better to select simple mode for developement and test
> enviroment.
> But I don't know excatly how can the full recovery model be usefull for
> critical enviroment?
> Can any body give me an example?
> Thanks alot
>|||maryam rezvani wrote:
> Hi
> What's the benefit usage to select Full recovery model for a database?
> I know it's better to select simple mode for developement and test
> enviroment.
> But I don't know excatly how can the full recovery model be usefull
> for critical enviroment?
> Can any body give me an example?
> Thanks alot
short:
if your DB is in full recovery model, you will have to backup the log, if
you can several times/day. In case of a restore, you probably will not lose
any data, and you can recovery to the point in time (useful if someone
deletes something or some other human error)
long:
see BooksOnLine (mssql help)|||Hi
By using 'FULL recovery' mode you will be able to restore your database at
point time
For example , you do a full backup on sunday night and every hour a log file
backup during the work day ,so on tuesday at 11 AM the database is crashed
.If you have the database in 'SIMPLE recovery' you will be able to get the
database back only from last backup (sunday night) ,that means you lost the
data of monday,tuesday . However , if you have 'FULL recovery' you have to
restore the last database backup and the apply all LOG backups till 11AM
(see more details in the BOL)
Another important point is
Let say you do a FULL backup database every sunday night and every hour a
LOG file backup. Now, you lost the FULL database backup of the second week
and the database is get corrupted now. So what would you do, you are about
to lost the data of two weeks ( if you do only FULL backup database (SIMPLE
recovery) ) ,but in that case you restore the last full backup (two weeks
ago) and the apply all LOG files you perfom till the corruption. You will
lost nothing because LOG file backup contains all info since last LOG file
backup.
"maryam rezvani" <rezvani@.parskhazar.net> wrote in message
news:uWJq1njwEHA.3824@.TK2MSFTNGP15.phx.gbl...
> Hi
> What's the benefit usage to select Full recovery model for a database?
> I know it's better to select simple mode for developement and test
> enviroment.
> But I don't know excatly how can the full recovery model be usefull for
> critical enviroment?
> Can any body give me an example?
> Thanks alot
>|||Thanks
Do you mean that if I found that some false insertion happenning to a
special table
in 9:00 am and my db is in full recovery model so I can restore my db to the
point
exaclty before the false insertion through the log file?
but if I set my db to simple mode have to restore the previous backup
related to the day before(cause I back up my db every night)?
"Zarko Jovanovic" <mind_less_NOSPAM_@.bigfoot.com> wrote in message
news:1099553502.722414@.internet.fina.hr...
> maryam rezvani wrote:
> short:
> if your DB is in full recovery model, you will have to backup the log, if
> you can several times/day. In case of a restore, you probably will not
lose
> any data, and you can recovery to the point in time (useful if someone
> deletes something or some other human error)
> long:
> see BooksOnLine (mssql help)
>|||Correct. But for the first scenario, you also need to perform regular transa
ction log backups. When
you restore a transaction log backup, you can stop at a certain point in tim
e.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"maryam rezvani" <rezvani@.parskhazar.net> wrote in message
news:egP72OkwEHA.4004@.tk2msftngp13.phx.gbl...
> Thanks
> Do you mean that if I found that some false insertion happenning to a
> special table
> in 9:00 am and my db is in full recovery model so I can restore my db to t
he
> point
> exaclty before the false insertion through the log file?
> but if I set my db to simple mode have to restore the previous backup
> related to the day before(cause I back up my db every night)?
> "Zarko Jovanovic" <mind_less_NOSPAM_@.bigfoot.com> wrote in message
> news:1099553502.722414@.internet.fina.hr...
> lose
>
benefits of full recovery**
Hi
What's the benefit usage to select Full recovery model for a database?
I know it's better to select simple mode for developement and test
enviroment.
But I don't know excatly how can the full recovery model be usefull for
critical enviroment?
Can any body give me an example?
Thanks alotMaryam,
Here is a nice article:
http://insight.zdnet.co.uk/software/developer/0,39020469,2134171-1,00.htm.
--
Dejan Sarka, SQL Server MVP
Associate Mentor
www.SolidQualityLearning.com
"maryam rezvani" <rezvani@.parskhazar.net> wrote in message
news:uWJq1njwEHA.3824@.TK2MSFTNGP15.phx.gbl...
> Hi
> What's the benefit usage to select Full recovery model for a database?
> I know it's better to select simple mode for developement and test
> enviroment.
> But I don't know excatly how can the full recovery model be usefull for
> critical enviroment?
> Can any body give me an example?
> Thanks alot
>|||maryam rezvani wrote:
> Hi
> What's the benefit usage to select Full recovery model for a database?
> I know it's better to select simple mode for developement and test
> enviroment.
> But I don't know excatly how can the full recovery model be usefull
> for critical enviroment?
> Can any body give me an example?
> Thanks alot
short:
if your DB is in full recovery model, you will have to backup the log, if
you can several times/day. In case of a restore, you probably will not lose
any data, and you can recovery to the point in time (useful if someone
deletes something or some other human error)
long:
see BooksOnLine (mssql help)|||Hi
By using 'FULL recovery' mode you will be able to restore your database at
point time
For example , you do a full backup on sunday night and every hour a log file
backup during the work day ,so on tuesday at 11 AM the database is crashed
.If you have the database in 'SIMPLE recovery' you will be able to get the
database back only from last backup (sunday night) ,that means you lost the
data of monday,tuesday . However , if you have 'FULL recovery' you have to
restore the last database backup and the apply all LOG backups till 11AM
(see more details in the BOL)
Another important point is
Let say you do a FULL backup database every sunday night and every hour a
LOG file backup. Now, you lost the FULL database backup of the second week
and the database is get corrupted now. So what would you do, you are about
to lost the data of two weeks ( if you do only FULL backup database (SIMPLE
recovery) ) ,but in that case you restore the last full backup (two weeks
ago) and the apply all LOG files you perfom till the corruption. You will
lost nothing because LOG file backup contains all info since last LOG file
backup.
"maryam rezvani" <rezvani@.parskhazar.net> wrote in message
news:uWJq1njwEHA.3824@.TK2MSFTNGP15.phx.gbl...
> Hi
> What's the benefit usage to select Full recovery model for a database?
> I know it's better to select simple mode for developement and test
> enviroment.
> But I don't know excatly how can the full recovery model be usefull for
> critical enviroment?
> Can any body give me an example?
> Thanks alot
>|||Thanks
Do you mean that if I found that some false insertion happenning to a
special table
in 9:00 am and my db is in full recovery model so I can restore my db to the
point
exaclty before the false insertion through the log file?
but if I set my db to simple mode have to restore the previous backup
related to the day before(cause I back up my db every night)?
"Zarko Jovanovic" <mind_less_NOSPAM_@.bigfoot.com> wrote in message
news:1099553502.722414@.internet.fina.hr...
> maryam rezvani wrote:
> > Hi
> >
> > What's the benefit usage to select Full recovery model for a database?
> > I know it's better to select simple mode for developement and test
> > enviroment.
> > But I don't know excatly how can the full recovery model be usefull
> > for critical enviroment?
> >
> > Can any body give me an example?
> > Thanks alot
> short:
> if your DB is in full recovery model, you will have to backup the log, if
> you can several times/day. In case of a restore, you probably will not
lose
> any data, and you can recovery to the point in time (useful if someone
> deletes something or some other human error)
> long:
> see BooksOnLine (mssql help)
>|||Correct. But for the first scenario, you also need to perform regular transaction log backups. When
you restore a transaction log backup, you can stop at a certain point in time.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"maryam rezvani" <rezvani@.parskhazar.net> wrote in message
news:egP72OkwEHA.4004@.tk2msftngp13.phx.gbl...
> Thanks
> Do you mean that if I found that some false insertion happenning to a
> special table
> in 9:00 am and my db is in full recovery model so I can restore my db to the
> point
> exaclty before the false insertion through the log file?
> but if I set my db to simple mode have to restore the previous backup
> related to the day before(cause I back up my db every night)?
> "Zarko Jovanovic" <mind_less_NOSPAM_@.bigfoot.com> wrote in message
> news:1099553502.722414@.internet.fina.hr...
> > maryam rezvani wrote:
> > > Hi
> > >
> > > What's the benefit usage to select Full recovery model for a database?
> > > I know it's better to select simple mode for developement and test
> > > enviroment.
> > > But I don't know excatly how can the full recovery model be usefull
> > > for critical enviroment?
> > >
> > > Can any body give me an example?
> > > Thanks alot
> >
> > short:
> >
> > if your DB is in full recovery model, you will have to backup the log, if
> > you can several times/day. In case of a restore, you probably will not
> lose
> > any data, and you can recovery to the point in time (useful if someone
> > deletes something or some other human error)
> >
> > long:
> >
> > see BooksOnLine (mssql help)
> >
> >
>
What's the benefit usage to select Full recovery model for a database?
I know it's better to select simple mode for developement and test
enviroment.
But I don't know excatly how can the full recovery model be usefull for
critical enviroment?
Can any body give me an example?
Thanks alotMaryam,
Here is a nice article:
http://insight.zdnet.co.uk/software/developer/0,39020469,2134171-1,00.htm.
--
Dejan Sarka, SQL Server MVP
Associate Mentor
www.SolidQualityLearning.com
"maryam rezvani" <rezvani@.parskhazar.net> wrote in message
news:uWJq1njwEHA.3824@.TK2MSFTNGP15.phx.gbl...
> Hi
> What's the benefit usage to select Full recovery model for a database?
> I know it's better to select simple mode for developement and test
> enviroment.
> But I don't know excatly how can the full recovery model be usefull for
> critical enviroment?
> Can any body give me an example?
> Thanks alot
>|||maryam rezvani wrote:
> Hi
> What's the benefit usage to select Full recovery model for a database?
> I know it's better to select simple mode for developement and test
> enviroment.
> But I don't know excatly how can the full recovery model be usefull
> for critical enviroment?
> Can any body give me an example?
> Thanks alot
short:
if your DB is in full recovery model, you will have to backup the log, if
you can several times/day. In case of a restore, you probably will not lose
any data, and you can recovery to the point in time (useful if someone
deletes something or some other human error)
long:
see BooksOnLine (mssql help)|||Hi
By using 'FULL recovery' mode you will be able to restore your database at
point time
For example , you do a full backup on sunday night and every hour a log file
backup during the work day ,so on tuesday at 11 AM the database is crashed
.If you have the database in 'SIMPLE recovery' you will be able to get the
database back only from last backup (sunday night) ,that means you lost the
data of monday,tuesday . However , if you have 'FULL recovery' you have to
restore the last database backup and the apply all LOG backups till 11AM
(see more details in the BOL)
Another important point is
Let say you do a FULL backup database every sunday night and every hour a
LOG file backup. Now, you lost the FULL database backup of the second week
and the database is get corrupted now. So what would you do, you are about
to lost the data of two weeks ( if you do only FULL backup database (SIMPLE
recovery) ) ,but in that case you restore the last full backup (two weeks
ago) and the apply all LOG files you perfom till the corruption. You will
lost nothing because LOG file backup contains all info since last LOG file
backup.
"maryam rezvani" <rezvani@.parskhazar.net> wrote in message
news:uWJq1njwEHA.3824@.TK2MSFTNGP15.phx.gbl...
> Hi
> What's the benefit usage to select Full recovery model for a database?
> I know it's better to select simple mode for developement and test
> enviroment.
> But I don't know excatly how can the full recovery model be usefull for
> critical enviroment?
> Can any body give me an example?
> Thanks alot
>|||Thanks
Do you mean that if I found that some false insertion happenning to a
special table
in 9:00 am and my db is in full recovery model so I can restore my db to the
point
exaclty before the false insertion through the log file?
but if I set my db to simple mode have to restore the previous backup
related to the day before(cause I back up my db every night)?
"Zarko Jovanovic" <mind_less_NOSPAM_@.bigfoot.com> wrote in message
news:1099553502.722414@.internet.fina.hr...
> maryam rezvani wrote:
> > Hi
> >
> > What's the benefit usage to select Full recovery model for a database?
> > I know it's better to select simple mode for developement and test
> > enviroment.
> > But I don't know excatly how can the full recovery model be usefull
> > for critical enviroment?
> >
> > Can any body give me an example?
> > Thanks alot
> short:
> if your DB is in full recovery model, you will have to backup the log, if
> you can several times/day. In case of a restore, you probably will not
lose
> any data, and you can recovery to the point in time (useful if someone
> deletes something or some other human error)
> long:
> see BooksOnLine (mssql help)
>|||Correct. But for the first scenario, you also need to perform regular transaction log backups. When
you restore a transaction log backup, you can stop at a certain point in time.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"maryam rezvani" <rezvani@.parskhazar.net> wrote in message
news:egP72OkwEHA.4004@.tk2msftngp13.phx.gbl...
> Thanks
> Do you mean that if I found that some false insertion happenning to a
> special table
> in 9:00 am and my db is in full recovery model so I can restore my db to the
> point
> exaclty before the false insertion through the log file?
> but if I set my db to simple mode have to restore the previous backup
> related to the day before(cause I back up my db every night)?
> "Zarko Jovanovic" <mind_less_NOSPAM_@.bigfoot.com> wrote in message
> news:1099553502.722414@.internet.fina.hr...
> > maryam rezvani wrote:
> > > Hi
> > >
> > > What's the benefit usage to select Full recovery model for a database?
> > > I know it's better to select simple mode for developement and test
> > > enviroment.
> > > But I don't know excatly how can the full recovery model be usefull
> > > for critical enviroment?
> > >
> > > Can any body give me an example?
> > > Thanks alot
> >
> > short:
> >
> > if your DB is in full recovery model, you will have to backup the log, if
> > you can several times/day. In case of a restore, you probably will not
> lose
> > any data, and you can recovery to the point in time (useful if someone
> > deletes something or some other human error)
> >
> > long:
> >
> > see BooksOnLine (mssql help)
> >
> >
>
Benchmark for different edition SQL 2000
We want to select the edition between standard and enterprise. Our usage
1) 10 users/application connect to the server at the same tim
2) 5000 row insert per da
3) Our machine is only 1CPU 2.6GHz and 512 MB RAM with window 2000 serve
4) One database will be installe
5) The size of the database around 10G
Because we want to replace the existing SQL6.5 with 400MHz 256MRAM database server
Please advise. ThanksHi,
Based on your configurations and settings I will recommend you to go for SQL
Server standard edition.
Have a look into the below link in choosing the edition of sql server:-
http://www.microsoft.com/sql/techinfo/planning/SQLReskChooseEd.asp
Thanks
Hari
MCDBA
"Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
news:08540023-9C99-4569-9A26-F765151912A2@.microsoft.com...
> We want to select the edition between standard and enterprise. Our usage:
> 1) 10 users/application connect to the server at the same time
> 2) 5000 row insert per day
> 3) Our machine is only 1CPU 2.6GHz and 512 MB RAM with window 2000 server
> 4) One database will be installed
> 5) The size of the database around 10GB
> Because we want to replace the existing SQL6.5 with 400MHz 256MRAM
database server.
> Please advise. Thanks|||Hari
Thanks for your advice. However, I have read the page before and without any idea. The point of availability is confused me. In fact, the standard edition and enterprise edition is no different except
--Scalability ( useless to us because we only have 1 CPU machine with 512MRAM
--Availability/uptime (useless to us because we don't have a standby or cluster machine
--Performance (Time is not so critical because we are just using the 6.5 version now with no complain
--Advanced analysis ( Analysis is not so critical because we are just using the 6.5 version now with no complain
I just concern, is it enterprise edition is more stable? or standard edition is easy to down
Wanchu
-- Hari Prasad wrote: --
Hi
Based on your configurations and settings I will recommend you to go for SQ
Server standard edition
Have a look into the below link in choosing the edition of sql server:
http://www.microsoft.com/sql/techinfo/planning/SQLReskChooseEd.as
Thank
Har
MCDB
"Wanchun" <anonymous@.discussions.microsoft.com> wrote in messag
news:08540023-9C99-4569-9A26-F765151912A2@.microsoft.com..
> We want to select the edition between standard and enterprise. Our usage
> 1) 10 users/application connect to the server at the same tim
> 2) 5000 row insert per da
> 3) Our machine is only 1CPU 2.6GHz and 512 MB RAM with window 2000 serve
> 4) One database will be installe
> 5) The size of the database around 10G
>> Because we want to replace the existing SQL6.5 with 400MHz 256MRA
database server
> Please advise. Thank|||No edition is any more or less stable than any others. It is mainly
features and capacity. Standard edition will do just fine for your needs.
--
Andrew J. Kelly SQL MVP
"Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
news:8E5E6311-B5DF-4D1E-9797-92DD6413C57C@.microsoft.com...
> Hari,
> Thanks for your advice. However, I have read the page before and without
any idea. The point of availability is confused me. In fact, the standard
edition and enterprise edition is no different except?
> --Scalability ( useless to us because we only have 1 CPU machine with
512MRAM)
> --Availability/uptime (useless to us because we don't have a standby or
cluster machine)
> --Performance (Time is not so critical because we are just using the 6.5
version now with no complain)
> --Advanced analysis ( Analysis is not so critical because we are just
using the 6.5 version now with no complain)
> I just concern, is it enterprise edition is more stable? or standard
edition is easy to down?
> Wanchun
>
> -- Hari Prasad wrote: --
> Hi,
> Based on your configurations and settings I will recommend you to go
for SQL
> Server standard edition.
> Have a look into the below link in choosing the edition of sql
server:-
> http://www.microsoft.com/sql/techinfo/planning/SQLReskChooseEd.asp
> Thanks
> Hari
> MCDBA
>
> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
> news:08540023-9C99-4569-9A26-F765151912A2@.microsoft.com...
> > We want to select the edition between standard and enterprise. Our
usage:
> > 1) 10 users/application connect to the server at the same time
> > 2) 5000 row insert per day
> > 3) Our machine is only 1CPU 2.6GHz and 512 MB RAM with window 2000
server
> > 4) One database will be installed
> > 5) The size of the database around 10GB
> >> Because we want to replace the existing SQL6.5 with 400MHz 256MRAM
> database server.
> > Please advise. Thanks
>
>|||Andrew
That mean from our requirement, standard edition is enough for us
Also, the memory arrangement is the same between standard and enterprise? I am testing with standard edition, the memory continue to grow from 10M to 110M after I inserted 3000 records. After I re-boot the machine, the memory back to 10M..... Is it I need to re-boot the machine every week to prevent the memory to grow' Or enterprise edition can handle it better
Any other Enterprise features that better than Standard
Thank
-- Andrew J. Kelly wrote: --
No edition is any more or less stable than any others. It is mainl
features and capacity. Standard edition will do just fine for your needs
--
Andrew J. Kelly SQL MV
"Wanchun" <anonymous@.discussions.microsoft.com> wrote in messag
news:8E5E6311-B5DF-4D1E-9797-92DD6413C57C@.microsoft.com..
> Hari
>> Thanks for your advice. However, I have read the page before and withou
any idea. The point of availability is confused me. In fact, the standar
edition and enterprise edition is no different except
>> --Scalability ( useless to us because we only have 1 CPU machine wit
512MRAM
> --Availability/uptime (useless to us because we don't have a standby o
cluster machine
> --Performance (Time is not so critical because we are just using the 6.
version now with no complain
> --Advanced analysis ( Analysis is not so critical because we are jus
using the 6.5 version now with no complain
>> I just concern, is it enterprise edition is more stable? or standar
edition is easy to down
>> Wanchu
>> -- Hari Prasad wrote: --
>> Hi
>> Based on your configurations and settings I will recommend you to g
for SQ
> Server standard edition
>> Have a look into the below link in choosing the edition of sq
server:
>> http://www.microsoft.com/sql/techinfo/planning/SQLReskChooseEd.as
>> Thank
> Har
> MCDB
>> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in messag
> news:08540023-9C99-4569-9A26-F765151912A2@.microsoft.com..
>> We want to select the edition between standard and enterprise. Ou
usage
>> 1) 10 users/application connect to the server at the same tim
>> 2) 5000 row insert per da
>> 3) Our machine is only 1CPU 2.6GHz and 512 MB RAM with window 200
serve
>> 4) One database will be installe
>> 5) The size of the database around 10G
>> Because we want to replace the existing SQL6.5 with 400MHz 256MRA
> database server
>> Please advise. Thank
>>|||Enterprise edition has some distinct features that SE doesn't. You find them at:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_ts_1cdv.asp
As for memory, please read below:
INF: SQL Server Memory Usage
http://support.microsoft.com/default.aspx?scid=kb;en-us;q321363
http://www.mssqlserver.com/faq/troubleshooting-memoryleak.asp
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
news:36E3DDB7-B674-4AFA-8A7C-3B7C1A336E3E@.microsoft.com...
> Andrew,
> That mean from our requirement, standard edition is enough for us?
> Also, the memory arrangement is the same between standard and enterprise? I am testing with standard
edition, the memory continue to grow from 10M to 110M after I inserted 3000 records. After I re-boot the
machine, the memory back to 10M..... Is it I need to re-boot the machine every week to prevent the memory to
grow' Or enterprise edition can handle it better?
> Any other Enterprise features that better than Standard?
> Thanks
>
>
> -- Andrew J. Kelly wrote: --
> No edition is any more or less stable than any others. It is mainly
> features and capacity. Standard edition will do just fine for your needs.
> --
> Andrew J. Kelly SQL MVP
>
> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
> news:8E5E6311-B5DF-4D1E-9797-92DD6413C57C@.microsoft.com...
> > Hari,
> >> Thanks for your advice. However, I have read the page before and without
> any idea. The point of availability is confused me. In fact, the standard
> edition and enterprise edition is no different except?
> >> --Scalability ( useless to us because we only have 1 CPU machine with
> 512MRAM)
> > --Availability/uptime (useless to us because we don't have a standby or
> cluster machine)
> > --Performance (Time is not so critical because we are just using the 6.5
> version now with no complain)
> > --Advanced analysis ( Analysis is not so critical because we are just
> using the 6.5 version now with no complain)
> >> I just concern, is it enterprise edition is more stable? or standard
> edition is easy to down?
> >> Wanchun
> >> -- Hari Prasad wrote: --
> >> Hi,
> >> Based on your configurations and settings I will recommend you to go
> for SQL
> > Server standard edition.
> >> Have a look into the below link in choosing the edition of sql
> server:-
> >> http://www.microsoft.com/sql/techinfo/planning/SQLReskChooseEd.asp
> >> Thanks
> > Hari
> > MCDBA
> >> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
> > news:08540023-9C99-4569-9A26-F765151912A2@.microsoft.com...
> >> We want to select the edition between standard and enterprise. Our
> usage:
> >> 1) 10 users/application connect to the server at the same time
> >> 2) 5000 row insert per day
> >> 3) Our machine is only 1CPU 2.6GHz and 512 MB RAM with window 2000
> server
> >> 4) One database will be installed
> >> 5) The size of the database around 10GB
> >> Because we want to replace the existing SQL6.5 with 400MHz 256MRAM
> > database server.
> >> Please advise. Thanks
> >>|||Tibor
My concern is how to prevent the SQL server that increase the memory usage continuously? Or We need to reboot the machine periodically? Please advise
Wanchu
-- Tibor Karaszi wrote: --
Enterprise edition has some distinct features that SE doesn't. You find them at
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_ts_1cdv.as
As for memory, please read below
INF: SQL Server Memory Usag
http://support.microsoft.com/default.aspx?scid=kb;en-us;q32136
http://www.mssqlserver.com/faq/troubleshooting-memoryleak.as
--
Tibor Karaszi, SQL Server MV
http://www.karaszi.com/sqlserver/default.as
http://www.solidqualitylearning.com
"Wanchun" <anonymous@.discussions.microsoft.com> wrote in messag
news:36E3DDB7-B674-4AFA-8A7C-3B7C1A336E3E@.microsoft.com..
> Andrew
>> That mean from our requirement, standard edition is enough for us
> Also, the memory arrangement is the same between standard and enterprise? I am testing with standar
edition, the memory continue to grow from 10M to 110M after I inserted 3000 records. After I re-boot th
machine, the memory back to 10M..... Is it I need to re-boot the machine every week to prevent the memory t
grow' Or enterprise edition can handle it better
>> Any other Enterprise features that better than Standard
>> Thank
>> -- Andrew J. Kelly wrote: --
>> No edition is any more or less stable than any others. It is mainl
> features and capacity. Standard edition will do just fine for your needs
>> --
> Andrew J. Kelly SQL MV
>> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in messag
> news:8E5E6311-B5DF-4D1E-9797-92DD6413C57C@.microsoft.com..
>> Hari
>> Thanks for your advice. However, I have read the page before and withou
> any idea. The point of availability is confused me. In fact, the standar
> edition and enterprise edition is no different except
>> --Scalability ( useless to us because we only have 1 CPU machine wit
> 512MRAM
>> --Availability/uptime (useless to us because we don't have a standby o
> cluster machine
>> --Performance (Time is not so critical because we are just using the 6.
> version now with no complain
>> --Advanced analysis ( Analysis is not so critical because we are jus
> using the 6.5 version now with no complain
>> I just concern, is it enterprise edition is more stable? or standar
> edition is easy to down
>> Wanchu
>> -- Hari Prasad wrote: --
>> Hi
>> Based on your configurations and settings I will recommend you to g
> for SQ
>> Server standard edition
>> Have a look into the below link in choosing the edition of sq
> server:
>> http://www.microsoft.com/sql/techinfo/planning/SQLReskChooseEd.as
>> Thank
>> Har
>> MCDB
>> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in messag
>> news:08540023-9C99-4569-9A26-F765151912A2@.microsoft.com..
>> We want to select the edition between standard and enterprise. Ou
> usage
>> 1) 10 users/application connect to the server at the same tim
>> 2) 5000 row insert per da
>> 3) Our machine is only 1CPU 2.6GHz and 512 MB RAM with window 200
> serve
>> 4) One database will be installe
>> 5) The size of the database around 10G
>> Because we want to replace the existing SQL6.5 with 400MHz 256MRA
>> database server
>> Please advise. Thank
>>|||Please read the links I posted about memory allocation algorithms in SQL Server. This is normal, and no reboot
is necessary.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
news:DF073FD2-4A17-4122-BCEC-E9FB5E5AF5EF@.microsoft.com...
> Tibor,
> My concern is how to prevent the SQL server that increase the memory usage continuously? Or We need to
reboot the machine periodically? Please advise.
> Wanchun
> -- Tibor Karaszi wrote: --
> Enterprise edition has some distinct features that SE doesn't. You find them at:
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_ts_1cdv.asp
> As for memory, please read below:
> INF: SQL Server Memory Usage
> http://support.microsoft.com/default.aspx?scid=kb;en-us;q321363
> http://www.mssqlserver.com/faq/troubleshooting-memoryleak.asp
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
> news:36E3DDB7-B674-4AFA-8A7C-3B7C1A336E3E@.microsoft.com...
> > Andrew,
> >> That mean from our requirement, standard edition is enough for us?
> > Also, the memory arrangement is the same between standard and enterprise? I am testing with standard
> edition, the memory continue to grow from 10M to 110M after I inserted 3000 records. After I re-boot
the
> machine, the memory back to 10M..... Is it I need to re-boot the machine every week to prevent the
memory to
> grow' Or enterprise edition can handle it better?
> >> Any other Enterprise features that better than Standard?
> >> Thanks
> >> -- Andrew J. Kelly wrote: --
> >> No edition is any more or less stable than any others. It is mainly
> > features and capacity. Standard edition will do just fine for your needs.
> >> --
> > Andrew J. Kelly SQL MVP
> >> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
> > news:8E5E6311-B5DF-4D1E-9797-92DD6413C57C@.microsoft.com...
> >> Hari,
> >> Thanks for your advice. However, I have read the page before and without
> > any idea. The point of availability is confused me. In fact, the standard
> > edition and enterprise edition is no different except?
> >> --Scalability ( useless to us because we only have 1 CPU machine with
> > 512MRAM)
> >> --Availability/uptime (useless to us because we don't have a standby or
> > cluster machine)
> >> --Performance (Time is not so critical because we are just using the 6.5
> > version now with no complain)
> >> --Advanced analysis ( Analysis is not so critical because we are just
> > using the 6.5 version now with no complain)
> >> I just concern, is it enterprise edition is more stable? or standard
> > edition is easy to down?
> >> Wanchun
> >> -- Hari Prasad wrote: --
> >> Hi,
> >> Based on your configurations and settings I will recommend you to go
> > for SQL
> >> Server standard edition.
> >> Have a look into the below link in choosing the edition of sql
> > server:-
> >> http://www.microsoft.com/sql/techinfo/planning/SQLReskChooseEd.asp
> >> Thanks
> >> Hari
> >> MCDBA
> >> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
> >> news:08540023-9C99-4569-9A26-F765151912A2@.microsoft.com...
> >> We want to select the edition between standard and enterprise. Our
> > usage:
> >> 1) 10 users/application connect to the server at the same time
> >> 2) 5000 row insert per day
> >> 3) Our machine is only 1CPU 2.6GHz and 512 MB RAM with window 2000
> > server
> >> 4) One database will be installed
> >> 5) The size of the database around 10GB
> >> Because we want to replace the existing SQL6.5 with 400MHz 256MRAM
> >> database server.
> >> Please advise. Thanks
> >>|||As Tibor points out that is normal behavior and will be the same for both
Std and EE.
Andrew J. Kelly SQL MVP
"Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
news:DF073FD2-4A17-4122-BCEC-E9FB5E5AF5EF@.microsoft.com...
> Tibor,
> My concern is how to prevent the SQL server that increase the memory
usage continuously? Or We need to reboot the machine periodically? Please
advise.
> Wanchun
> -- Tibor Karaszi wrote: --
> Enterprise edition has some distinct features that SE doesn't. You
find them at:
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_ts_1cdv.asp
> As for memory, please read below:
> INF: SQL Server Memory Usage
> http://support.microsoft.com/default.aspx?scid=kb;en-us;q321363
> http://www.mssqlserver.com/faq/troubleshooting-memoryleak.asp
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
> news:36E3DDB7-B674-4AFA-8A7C-3B7C1A336E3E@.microsoft.com...
> > Andrew,
> >> That mean from our requirement, standard edition is enough for us?
> > Also, the memory arrangement is the same between standard and
enterprise? I am testing with standard
> edition, the memory continue to grow from 10M to 110M after I
inserted 3000 records. After I re-boot the
> machine, the memory back to 10M..... Is it I need to re-boot the
machine every week to prevent the memory to
> grow' Or enterprise edition can handle it better?
> >> Any other Enterprise features that better than Standard?
> >> Thanks
> >> -- Andrew J. Kelly wrote: --
> >> No edition is any more or less stable than any others. It is
mainly
> > features and capacity. Standard edition will do just fine for
your needs.
> >> --
> > Andrew J. Kelly SQL MVP
> >> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in
message
> > news:8E5E6311-B5DF-4D1E-9797-92DD6413C57C@.microsoft.com...
> >> Hari,
> >> Thanks for your advice. However, I have read the page before and
without
> > any idea. The point of availability is confused me. In fact,
the standard
> > edition and enterprise edition is no different except?
> >> --Scalability ( useless to us because we only have 1 CPU machine
with
> > 512MRAM)
> >> --Availability/uptime (useless to us because we don't have a
standby or
> > cluster machine)
> >> --Performance (Time is not so critical because we are just using
the 6.5
> > version now with no complain)
> >> --Advanced analysis ( Analysis is not so critical because we are
just
> > using the 6.5 version now with no complain)
> >> I just concern, is it enterprise edition is more stable? or
standard
> > edition is easy to down?
> >> Wanchun
> >> -- Hari Prasad wrote: --
> >> Hi,
> >> Based on your configurations and settings I will recommend
you to go
> > for SQL
> >> Server standard edition.
> >> Have a look into the below link in choosing the edition of
sql
> > server:-
> >>
http://www.microsoft.com/sql/techinfo/planning/SQLReskChooseEd.asp
> >> Thanks
> >> Hari
> >> MCDBA
> >> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in
message
> >> news:08540023-9C99-4569-9A26-F765151912A2@.microsoft.com...
> >> We want to select the edition between standard and enterprise.
Our
> > usage:
> >> 1) 10 users/application connect to the server at the same time
> >> 2) 5000 row insert per day
> >> 3) Our machine is only 1CPU 2.6GHz and 512 MB RAM with window
2000
> > server
> >> 4) One database will be installed
> >> 5) The size of the database around 10GB
> >> Because we want to replace the existing SQL6.5 with 400MHz
256MRAM
> >> database server.
> >> Please advise. Thanks
> >>|||Thanks again Tibor, however, if SQL used all the physical memory of the machine, then the SQL can still run smoothly? or better reboot the machine
Wanchu
-- Tibor Karaszi wrote: --
Please read the links I posted about memory allocation algorithms in SQL Server. This is normal, and no reboo
is necessary
--
Tibor Karaszi, SQL Server MV
http://www.karaszi.com/sqlserver/default.as
http://www.solidqualitylearning.com
"Wanchun" <anonymous@.discussions.microsoft.com> wrote in messag
news:DF073FD2-4A17-4122-BCEC-E9FB5E5AF5EF@.microsoft.com..
> Tibor
> My concern is how to prevent the SQL server that increase the memory usage continuously? Or We need t
reboot the machine periodically? Please advise
>> Wanchu
>> -- Tibor Karaszi wrote: --
>> Enterprise edition has some distinct features that SE doesn't. You find them at
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_ts_1cdv.as
>> As for memory, please read below
>> INF: SQL Server Memory Usag
> http://support.microsoft.com/default.aspx?scid=kb;en-us;q32136
>> http://www.mssqlserver.com/faq/troubleshooting-memoryleak.as
>> --
> Tibor Karaszi, SQL Server MV
> http://www.karaszi.com/sqlserver/default.as
> http://www.solidqualitylearning.com
>> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in messag
> news:36E3DDB7-B674-4AFA-8A7C-3B7C1A336E3E@.microsoft.com..
>> Andrew
>> That mean from our requirement, standard edition is enough for us
>> Also, the memory arrangement is the same between standard and enterprise? I am testing with standar
> edition, the memory continue to grow from 10M to 110M after I inserted 3000 records. After I re-boo
th
> machine, the memory back to 10M..... Is it I need to re-boot the machine every week to prevent th
memory t
> grow' Or enterprise edition can handle it better
>> Any other Enterprise features that better than Standard
>> Thank
>>> -- Andrew J. Kelly wrote: --
>> No edition is any more or less stable than any others. It is mainl
>> features and capacity. Standard edition will do just fine for your needs
>> --
>> Andrew J. Kelly SQL MV
>> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in messag
>> news:8E5E6311-B5DF-4D1E-9797-92DD6413C57C@.microsoft.com..
>> Hari
>> Thanks for your advice. However, I have read the page before and withou
>> any idea. The point of availability is confused me. In fact, the standar
>> edition and enterprise edition is no different except
>> --Scalability ( useless to us because we only have 1 CPU machine wit
>> 512MRAM
>> --Availability/uptime (useless to us because we don't have a standby o
>> cluster machine
>> --Performance (Time is not so critical because we are just using the 6.
>> version now with no complain
>> --Advanced analysis ( Analysis is not so critical because we are jus
>> using the 6.5 version now with no complain
>> I just concern, is it enterprise edition is more stable? or standar
>> edition is easy to down
>> Wanchu
>> -- Hari Prasad wrote: --
>> Hi
>> Based on your configurations and settings I will recommend you to g
>> for SQ
>> Server standard edition
>> Have a look into the below link in choosing the edition of sq
>> server:
>> http://www.microsoft.com/sql/techinfo/planning/SQLReskChooseEd.as
>> Thank
>> Har
>> MCDB
>> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in messag
>> news:08540023-9C99-4569-9A26-F765151912A2@.microsoft.com..
>> We want to select the edition between standard and enterprise. Our
>> usage:
>> 1) 10 users/application connect to the server at the same time
>> 2) 5000 row insert per day
>> 3) Our machine is only 1CPU 2.6GHz and 512 MB RAM with window 2000
>> server
>> 4) One database will be installed
>> 5) The size of the database around 10GB
>> Because we want to replace the existing SQL6.5 with 400MHz 256MRAM
>> database server.
>> Please advise. Thanks
>>|||The purpose if buying memory is for it to be used. SQL Server does just that. Yes, it is normal for a SQL
Server installation to see all memory being used. :-)
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Wanhcun" <anonymous@.discussions.microsoft.com> wrote in message
news:70CBBAD5-7E54-4EB8-9A9C-3EBDEBF2A674@.microsoft.com...
> Thanks again Tibor, however, if SQL used all the physical memory of the machine, then the SQL can still run
smoothly? or better reboot the machine?
> Wanchun
> -- Tibor Karaszi wrote: --
> Please read the links I posted about memory allocation algorithms in SQL Server. This is normal, and no
reboot
> is necessary.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
> news:DF073FD2-4A17-4122-BCEC-E9FB5E5AF5EF@.microsoft.com...
> > Tibor,
> > My concern is how to prevent the SQL server that increase the memory usage continuously? Or We
need to
> reboot the machine periodically? Please advise.
> >> Wanchun
> >> -- Tibor Karaszi wrote: --
> >> Enterprise edition has some distinct features that SE doesn't. You find them at:
> > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_ts_1cdv.asp
> >> As for memory, please read below:
> >> INF: SQL Server Memory Usage
> > http://support.microsoft.com/default.aspx?scid=kb;en-us;q321363
> >> http://www.mssqlserver.com/faq/troubleshooting-memoryleak.asp
> >> --
> > Tibor Karaszi, SQL Server MVP
> > http://www.karaszi.com/sqlserver/default.asp
> > http://www.solidqualitylearning.com/
> >> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
> > news:36E3DDB7-B674-4AFA-8A7C-3B7C1A336E3E@.microsoft.com...
> >> Andrew,
> >> That mean from our requirement, standard edition is enough for us?
> >> Also, the memory arrangement is the same between standard and enterprise? I am testing with standard
> > edition, the memory continue to grow from 10M to 110M after I inserted 3000 records. After I
re-boot
> the
> > machine, the memory back to 10M..... Is it I need to re-boot the machine every week to prevent
the
> memory to
> > grow' Or enterprise edition can handle it better?
> >> Any other Enterprise features that better than Standard?
> >> Thanks
> >>> -- Andrew J. Kelly wrote: --
> >> No edition is any more or less stable than any others. It is mainly
> >> features and capacity. Standard edition will do just fine for your needs.
> >> --
> >> Andrew J. Kelly SQL MVP
> >> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
> >> news:8E5E6311-B5DF-4D1E-9797-92DD6413C57C@.microsoft.com...
> >> Hari,
> >> Thanks for your advice. However, I have read the page before and without
> >> any idea. The point of availability is confused me. In fact, the standard
> >> edition and enterprise edition is no different except?
> >> --Scalability ( useless to us because we only have 1 CPU machine with
> >> 512MRAM)
> >> --Availability/uptime (useless to us because we don't have a standby or
> >> cluster machine)
> >> --Performance (Time is not so critical because we are just using the 6.5
> >> version now with no complain)
> >> --Advanced analysis ( Analysis is not so critical because we are just
> >> using the 6.5 version now with no complain)
> >> I just concern, is it enterprise edition is more stable? or standard
> >> edition is easy to down?
> >> Wanchun
> >> -- Hari Prasad wrote: --
> >> Hi,
> >> Based on your configurations and settings I will recommend you to go
> >> for SQL
> >> Server standard edition.
> >> Have a look into the below link in choosing the edition of sql
> >> server:-
> >> http://www.microsoft.com/sql/techinfo/planning/SQLReskChooseEd.asp
> >> Thanks
> >> Hari
> >> MCDBA
> >> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
> >> news:08540023-9C99-4569-9A26-F765151912A2@.microsoft.com...
> >> We want to select the edition between standard and enterprise. Our
> >> usage:
> >> 1) 10 users/application connect to the server at the same time
> >> 2) 5000 row insert per day
> >> 3) Our machine is only 1CPU 2.6GHz and 512 MB RAM with window 2000
> >> server
> >> 4) One database will be installed
> >> 5) The size of the database around 10GB
> >> Because we want to replace the existing SQL6.5 with 400MHz 256MRAM
> >> database server.
> >> Please advise. Thanks
> >>|||Tibor
This is because my machine only contain 512 MRAM... then we need to set the "maximun memory" of SQL server around 400M and let 100M memory that can be used by the OS? Please advise.Thanks...
Regards
Wanchu
-- Tibor Karaszi wrote: --
The purpose if buying memory is for it to be used. SQL Server does just that. Yes, it is normal for a SQ
Server installation to see all memory being used. :-
--
Tibor Karaszi, SQL Server MV
http://www.karaszi.com/sqlserver/default.as
http://www.solidqualitylearning.com
"Wanhcun" <anonymous@.discussions.microsoft.com> wrote in messag
news:70CBBAD5-7E54-4EB8-9A9C-3EBDEBF2A674@.microsoft.com..
> Thanks again Tibor, however, if SQL used all the physical memory of the machine, then the SQL can still ru
smoothly? or better reboot the machine
>> Wanchu
>> -- Tibor Karaszi wrote: --
>> Please read the links I posted about memory allocation algorithms in SQL Server. This is normal, and n
reboo
> is necessary
>> --
> Tibor Karaszi, SQL Server MV
> http://www.karaszi.com/sqlserver/default.as
> http://www.solidqualitylearning.com
>> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in messag
> news:DF073FD2-4A17-4122-BCEC-E9FB5E5AF5EF@.microsoft.com..
>> Tibor
>> My concern is how to prevent the SQL server that increase the memory usage continuously? Or W
need t
> reboot the machine periodically? Please advise
>> Wanchu
>> -- Tibor Karaszi wrote: --
>> Enterprise edition has some distinct features that SE doesn't. You find them at
>> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_ts_1cdv.as
>> As for memory, please read below
>> INF: SQL Server Memory Usag
>> http://support.microsoft.com/default.aspx?scid=kb;en-us;q32136
>> http://www.mssqlserver.com/faq/troubleshooting-memoryleak.as
>> --
>> Tibor Karaszi, SQL Server MV
>> http://www.karaszi.com/sqlserver/default.as
>> http://www.solidqualitylearning.com
>> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in messag
>> news:36E3DDB7-B674-4AFA-8A7C-3B7C1A336E3E@.microsoft.com..
>> Andrew
>> That mean from our requirement, standard edition is enough for us
>> Also, the memory arrangement is the same between standard and enterprise? I am testing with standar
>> edition, the memory continue to grow from 10M to 110M after I inserted 3000 records. After
re-boo
> th
>> machine, the memory back to 10M..... Is it I need to re-boot the machine every week to preven
th
> memory t
>> grow' Or enterprise edition can handle it better
>> Any other Enterprise features that better than Standard
>> Thank
>>> -- Andrew J. Kelly wrote: --
>> No edition is any more or less stable than any others. It is mainl
>> features and capacity. Standard edition will do just fine for your needs
>> --
>> Andrew J. Kelly SQL MV
>> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in messag
>> news:8E5E6311-B5DF-4D1E-9797-92DD6413C57C@.microsoft.com..
>> Hari
>> Thanks for your advice. However, I have read the page before and withou
>> any idea. The point of availability is confused me. In fact, the standar
>> edition and enterprise edition is no different except
>> --Scalability ( useless to us because we only have 1 CPU machine wit
>> 512MRAM
>> --Availability/uptime (useless to us because we don't have a standby o
>> cluster machine
>> --Performance (Time is not so critical because we are just using the 6.
>> version now with no complain
>> --Advanced analysis ( Analysis is not so critical because we are just
>> using the 6.5 version now with no complain)
>> I just concern, is it enterprise edition is more stable? or standard
>> edition is easy to down?
>> Wanchun
>> -- Hari Prasad wrote: --
>> Hi,
>> Based on your configurations and settings I will recommend you to go
>> for SQL
>> Server standard edition.
>> Have a look into the below link in choosing the edition of sql
>> server:-
>> http://www.microsoft.com/sql/techinfo/planning/SQLReskChooseEd.asp
>> Thanks
>> Hari
>> MCDBA
>>> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
>> news:08540023-9C99-4569-9A26-F765151912A2@.microsoft.com...
>> We want to select the edition between standard and enterprise. Our
>> usage:
>> 1) 10 users/application connect to the server at the same time
>> 2) 5000 row insert per day
>> 3) Our machine is only 1CPU 2.6GHz and 512 MB RAM with window 2000
>> server
>> 4) One database will be installed
>> 5) The size of the database around 10GB
>> Because we want to replace the existing SQL6.5 with 400MHz 256MRAM
>> database server.
>> Please advise. Thanks
>>|||The fact that you only have 512 MB doesn't change the memory allocation algorithms. SQL Server will use the
memory in the machine (but of course leave space for OS and a little bit more). But sure, you can set a max if
you absolutely want to...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
news:3D73FA4A-D85C-40BF-BC30-D2F32E57602B@.microsoft.com...
> Tibor,
> This is because my machine only contain 512 MRAM... then we need to set the "maximun memory" of SQL server
around 400M and let 100M memory that can be used by the OS? Please advise.Thanks....
> Regards,
> Wanchun
> -- Tibor Karaszi wrote: --
> The purpose if buying memory is for it to be used. SQL Server does just that. Yes, it is normal for a
SQL
> Server installation to see all memory being used. :-)
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Wanhcun" <anonymous@.discussions.microsoft.com> wrote in message
> news:70CBBAD5-7E54-4EB8-9A9C-3EBDEBF2A674@.microsoft.com...
> > Thanks again Tibor, however, if SQL used all the physical memory of the machine, then the SQL can
still run
> smoothly? or better reboot the machine?
> >> Wanchun
> >> -- Tibor Karaszi wrote: --
> >> Please read the links I posted about memory allocation algorithms in SQL Server. This is
normal, and no
> reboot
> > is necessary.
> >> --
> > Tibor Karaszi, SQL Server MVP
> > http://www.karaszi.com/sqlserver/default.asp
> > http://www.solidqualitylearning.com/
> >> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
> > news:DF073FD2-4A17-4122-BCEC-E9FB5E5AF5EF@.microsoft.com...
> >> Tibor,
> >> My concern is how to prevent the SQL server that increase the memory usage continuously? Or We
> need to
> > reboot the machine periodically? Please advise.
> >> Wanchun
> >> -- Tibor Karaszi wrote: --
> >> Enterprise edition has some distinct features that SE doesn't. You find them at:
> >> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_ts_1cdv.asp
> >> As for memory, please read below:
> >> INF: SQL Server Memory Usage
> >> http://support.microsoft.com/default.aspx?scid=kb;en-us;q321363
> >> http://www.mssqlserver.com/faq/troubleshooting-memoryleak.asp
> >> --
> >> Tibor Karaszi, SQL Server MVP
> >> http://www.karaszi.com/sqlserver/default.asp
> >> http://www.solidqualitylearning.com/
> >> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
> >> news:36E3DDB7-B674-4AFA-8A7C-3B7C1A336E3E@.microsoft.com...
> >> Andrew,
> >> That mean from our requirement, standard edition is enough for us?
> >> Also, the memory arrangement is the same between standard and enterprise? I am testing with
standard
> >> edition, the memory continue to grow from 10M to 110M after I inserted 3000 records. After I
> re-boot
> > the
> >> machine, the memory back to 10M..... Is it I need to re-boot the machine every week to prevent
> the
> > memory to
> >> grow' Or enterprise edition can handle it better?
> >> Any other Enterprise features that better than Standard?
> >> Thanks
> >>> -- Andrew J. Kelly wrote: --
> >> No edition is any more or less stable than any others. It is mainly
> >> features and capacity. Standard edition will do just fine for your needs.
> >> --
> >> Andrew J. Kelly SQL MVP
> >> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
> >> news:8E5E6311-B5DF-4D1E-9797-92DD6413C57C@.microsoft.com...
> >> Hari,
> >> Thanks for your advice. However, I have read the page before and without
> >> any idea. The point of availability is confused me. In fact, the standard
> >> edition and enterprise edition is no different except?
> >> --Scalability ( useless to us because we only have 1 CPU machine with
> >> 512MRAM)
> >> --Availability/uptime (useless to us because we don't have a standby or
> >> cluster machine)
> >> --Performance (Time is not so critical because we are just using the 6.5
> >> version now with no complain)
> >> --Advanced analysis ( Analysis is not so critical because we are just
> >> using the 6.5 version now with no complain)
> >> I just concern, is it enterprise edition is more stable? or standard
> >> edition is easy to down?
> >> Wanchun
> >> -- Hari Prasad wrote: --
> >> Hi,
> >> Based on your configurations and settings I will recommend you to go
> >> for SQL
> >> Server standard edition.
> >> Have a look into the below link in choosing the edition of sql
> >> server:-
> >> http://www.microsoft.com/sql/techinfo/planning/SQLReskChooseEd.asp
> >> Thanks
> >> Hari
> >> MCDBA
> >>> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
> >> news:08540023-9C99-4569-9A26-F765151912A2@.microsoft.com...
> >> We want to select the edition between standard and enterprise. Our
> >> usage:
> >> 1) 10 users/application connect to the server at the same time
> >> 2) 5000 row insert per day
> >> 3) Our machine is only 1CPU 2.6GHz and 512 MB RAM with window 2000
> >> server
> >> 4) One database will be installed
> >> 5) The size of the database around 10GB
> >> Because we want to replace the existing SQL6.5 with 400MHz 256MRAM
> >> database server.
> >> Please advise. Thanks
> >>|||The max memory only sets an upper limit for the memory pool. There is an
area called the mem to leave that gets allocated first. By default it can
use to to 256MB so if you set the max memory to 400 you will most likely
still swap with the OS. While it may be better than not changing anything I
would set it even lower. You stated you only do 5000 inserts a day so you
should not require a lot of memory to operate properly. Try setting it to
300MB and see if that helps. Memory is cheap these days and you might want
to look into adding more later on.
--
Andrew J. Kelly SQL MVP
"Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
news:3D73FA4A-D85C-40BF-BC30-D2F32E57602B@.microsoft.com...
> Tibor,
> This is because my machine only contain 512 MRAM... then we need to set
the "maximun memory" of SQL server around 400M and let 100M memory that can
be used by the OS? Please advise.Thanks....
> Regards,
> Wanchun
> -- Tibor Karaszi wrote: --
> The purpose if buying memory is for it to be used. SQL Server does
just that. Yes, it is normal for a SQL
> Server installation to see all memory being used. :-)
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Wanhcun" <anonymous@.discussions.microsoft.com> wrote in message
> news:70CBBAD5-7E54-4EB8-9A9C-3EBDEBF2A674@.microsoft.com...
> > Thanks again Tibor, however, if SQL used all the physical memory of
the machine, then the SQL can still run
> smoothly? or better reboot the machine?
> >> Wanchun
> >> -- Tibor Karaszi wrote: --
> >> Please read the links I posted about memory allocation
algorithms in SQL Server. This is normal, and no
> reboot
> > is necessary.
> >> --
> > Tibor Karaszi, SQL Server MVP
> > http://www.karaszi.com/sqlserver/default.asp
> > http://www.solidqualitylearning.com/
> >> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in
message
> > news:DF073FD2-4A17-4122-BCEC-E9FB5E5AF5EF@.microsoft.com...
> >> Tibor,
> >> My concern is how to prevent the SQL server that increase the
memory usage continuously? Or We
> need to
> > reboot the machine periodically? Please advise.
> >> Wanchun
> >> -- Tibor Karaszi wrote: --
> >> Enterprise edition has some distinct features that SE
doesn't. You find them at:
> >>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_ts_1cdv.asp
> >> As for memory, please read below:
> >> INF: SQL Server Memory Usage
> >>
http://support.microsoft.com/default.aspx?scid=kb;en-us;q321363
> >>
http://www.mssqlserver.com/faq/troubleshooting-memoryleak.asp
> >> --
> >> Tibor Karaszi, SQL Server MVP
> >> http://www.karaszi.com/sqlserver/default.asp
> >> http://www.solidqualitylearning.com/
> >> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in
message
> >> news:36E3DDB7-B674-4AFA-8A7C-3B7C1A336E3E@.microsoft.com...
> >> Andrew,
> >> That mean from our requirement, standard edition is enough for
us?
> >> Also, the memory arrangement is the same between standard and
enterprise? I am testing with standard
> >> edition, the memory continue to grow from 10M to 110M after I
inserted 3000 records. After I
> re-boot
> > the
> >> machine, the memory back to 10M..... Is it I need to re-boot
the machine every week to prevent
> the
> > memory to
> >> grow' Or enterprise edition can handle it better?
> >> Any other Enterprise features that better than Standard?
> >> Thanks
> >>> -- Andrew J. Kelly wrote: --
> >> No edition is any more or less stable than any others. It
is mainly
> >> features and capacity. Standard edition will do just fine
for your needs.
> >> --
> >> Andrew J. Kelly SQL MVP
> >> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in
message
> >> news:8E5E6311-B5DF-4D1E-9797-92DD6413C57C@.microsoft.com...
> >> Hari,
> >> Thanks for your advice. However, I have read the page before
and without
> >> any idea. The point of availability is confused me. In fact,
the standard
> >> edition and enterprise edition is no different except?
> >> --Scalability ( useless to us because we only have 1 CPU
machine with
> >> 512MRAM)
> >> --Availability/uptime (useless to us because we don't have a
standby or
> >> cluster machine)
> >> --Performance (Time is not so critical because we are just using
the 6.5
> >> version now with no complain)
> >> --Advanced analysis ( Analysis is not so critical because we are
just
> >> using the 6.5 version now with no complain)
> >> I just concern, is it enterprise edition is more stable? or
standard
> >> edition is easy to down?
> >> Wanchun
> >> -- Hari Prasad wrote: --
> >> Hi,
> >> Based on your configurations and settings I will recommend
you to go
> >> for SQL
> >> Server standard edition.
> >> Have a look into the below link in choosing the edition of
sql
> >> server:-
> >>
http://www.microsoft.com/sql/techinfo/planning/SQLReskChooseEd.asp
> >> Thanks
> >> Hari
> >> MCDBA
> >>> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in
message
> >> news:08540023-9C99-4569-9A26-F765151912A2@.microsoft.com...
> >> We want to select the edition between standard and enterprise.
Our
> >> usage:
> >> 1) 10 users/application connect to the server at the same time
> >> 2) 5000 row insert per day
> >> 3) Our machine is only 1CPU 2.6GHz and 512 MB RAM with window
2000
> >> server
> >> 4) One database will be installed
> >> 5) The size of the database around 10GB
> >> Because we want to replace the existing SQL6.5 with 400MHz
256MRAM
> >> database server.
> >> Please advise. Thanks
> >>
1) 10 users/application connect to the server at the same tim
2) 5000 row insert per da
3) Our machine is only 1CPU 2.6GHz and 512 MB RAM with window 2000 serve
4) One database will be installe
5) The size of the database around 10G
Because we want to replace the existing SQL6.5 with 400MHz 256MRAM database server
Please advise. ThanksHi,
Based on your configurations and settings I will recommend you to go for SQL
Server standard edition.
Have a look into the below link in choosing the edition of sql server:-
http://www.microsoft.com/sql/techinfo/planning/SQLReskChooseEd.asp
Thanks
Hari
MCDBA
"Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
news:08540023-9C99-4569-9A26-F765151912A2@.microsoft.com...
> We want to select the edition between standard and enterprise. Our usage:
> 1) 10 users/application connect to the server at the same time
> 2) 5000 row insert per day
> 3) Our machine is only 1CPU 2.6GHz and 512 MB RAM with window 2000 server
> 4) One database will be installed
> 5) The size of the database around 10GB
> Because we want to replace the existing SQL6.5 with 400MHz 256MRAM
database server.
> Please advise. Thanks|||Hari
Thanks for your advice. However, I have read the page before and without any idea. The point of availability is confused me. In fact, the standard edition and enterprise edition is no different except
--Scalability ( useless to us because we only have 1 CPU machine with 512MRAM
--Availability/uptime (useless to us because we don't have a standby or cluster machine
--Performance (Time is not so critical because we are just using the 6.5 version now with no complain
--Advanced analysis ( Analysis is not so critical because we are just using the 6.5 version now with no complain
I just concern, is it enterprise edition is more stable? or standard edition is easy to down
Wanchu
-- Hari Prasad wrote: --
Hi
Based on your configurations and settings I will recommend you to go for SQ
Server standard edition
Have a look into the below link in choosing the edition of sql server:
http://www.microsoft.com/sql/techinfo/planning/SQLReskChooseEd.as
Thank
Har
MCDB
"Wanchun" <anonymous@.discussions.microsoft.com> wrote in messag
news:08540023-9C99-4569-9A26-F765151912A2@.microsoft.com..
> We want to select the edition between standard and enterprise. Our usage
> 1) 10 users/application connect to the server at the same tim
> 2) 5000 row insert per da
> 3) Our machine is only 1CPU 2.6GHz and 512 MB RAM with window 2000 serve
> 4) One database will be installe
> 5) The size of the database around 10G
>> Because we want to replace the existing SQL6.5 with 400MHz 256MRA
database server
> Please advise. Thank|||No edition is any more or less stable than any others. It is mainly
features and capacity. Standard edition will do just fine for your needs.
--
Andrew J. Kelly SQL MVP
"Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
news:8E5E6311-B5DF-4D1E-9797-92DD6413C57C@.microsoft.com...
> Hari,
> Thanks for your advice. However, I have read the page before and without
any idea. The point of availability is confused me. In fact, the standard
edition and enterprise edition is no different except?
> --Scalability ( useless to us because we only have 1 CPU machine with
512MRAM)
> --Availability/uptime (useless to us because we don't have a standby or
cluster machine)
> --Performance (Time is not so critical because we are just using the 6.5
version now with no complain)
> --Advanced analysis ( Analysis is not so critical because we are just
using the 6.5 version now with no complain)
> I just concern, is it enterprise edition is more stable? or standard
edition is easy to down?
> Wanchun
>
> -- Hari Prasad wrote: --
> Hi,
> Based on your configurations and settings I will recommend you to go
for SQL
> Server standard edition.
> Have a look into the below link in choosing the edition of sql
server:-
> http://www.microsoft.com/sql/techinfo/planning/SQLReskChooseEd.asp
> Thanks
> Hari
> MCDBA
>
> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
> news:08540023-9C99-4569-9A26-F765151912A2@.microsoft.com...
> > We want to select the edition between standard and enterprise. Our
usage:
> > 1) 10 users/application connect to the server at the same time
> > 2) 5000 row insert per day
> > 3) Our machine is only 1CPU 2.6GHz and 512 MB RAM with window 2000
server
> > 4) One database will be installed
> > 5) The size of the database around 10GB
> >> Because we want to replace the existing SQL6.5 with 400MHz 256MRAM
> database server.
> > Please advise. Thanks
>
>|||Andrew
That mean from our requirement, standard edition is enough for us
Also, the memory arrangement is the same between standard and enterprise? I am testing with standard edition, the memory continue to grow from 10M to 110M after I inserted 3000 records. After I re-boot the machine, the memory back to 10M..... Is it I need to re-boot the machine every week to prevent the memory to grow' Or enterprise edition can handle it better
Any other Enterprise features that better than Standard
Thank
-- Andrew J. Kelly wrote: --
No edition is any more or less stable than any others. It is mainl
features and capacity. Standard edition will do just fine for your needs
--
Andrew J. Kelly SQL MV
"Wanchun" <anonymous@.discussions.microsoft.com> wrote in messag
news:8E5E6311-B5DF-4D1E-9797-92DD6413C57C@.microsoft.com..
> Hari
>> Thanks for your advice. However, I have read the page before and withou
any idea. The point of availability is confused me. In fact, the standar
edition and enterprise edition is no different except
>> --Scalability ( useless to us because we only have 1 CPU machine wit
512MRAM
> --Availability/uptime (useless to us because we don't have a standby o
cluster machine
> --Performance (Time is not so critical because we are just using the 6.
version now with no complain
> --Advanced analysis ( Analysis is not so critical because we are jus
using the 6.5 version now with no complain
>> I just concern, is it enterprise edition is more stable? or standar
edition is easy to down
>> Wanchu
>> -- Hari Prasad wrote: --
>> Hi
>> Based on your configurations and settings I will recommend you to g
for SQ
> Server standard edition
>> Have a look into the below link in choosing the edition of sq
server:
>> http://www.microsoft.com/sql/techinfo/planning/SQLReskChooseEd.as
>> Thank
> Har
> MCDB
>> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in messag
> news:08540023-9C99-4569-9A26-F765151912A2@.microsoft.com..
>> We want to select the edition between standard and enterprise. Ou
usage
>> 1) 10 users/application connect to the server at the same tim
>> 2) 5000 row insert per da
>> 3) Our machine is only 1CPU 2.6GHz and 512 MB RAM with window 200
serve
>> 4) One database will be installe
>> 5) The size of the database around 10G
>> Because we want to replace the existing SQL6.5 with 400MHz 256MRA
> database server
>> Please advise. Thank
>>|||Enterprise edition has some distinct features that SE doesn't. You find them at:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_ts_1cdv.asp
As for memory, please read below:
INF: SQL Server Memory Usage
http://support.microsoft.com/default.aspx?scid=kb;en-us;q321363
http://www.mssqlserver.com/faq/troubleshooting-memoryleak.asp
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
news:36E3DDB7-B674-4AFA-8A7C-3B7C1A336E3E@.microsoft.com...
> Andrew,
> That mean from our requirement, standard edition is enough for us?
> Also, the memory arrangement is the same between standard and enterprise? I am testing with standard
edition, the memory continue to grow from 10M to 110M after I inserted 3000 records. After I re-boot the
machine, the memory back to 10M..... Is it I need to re-boot the machine every week to prevent the memory to
grow' Or enterprise edition can handle it better?
> Any other Enterprise features that better than Standard?
> Thanks
>
>
> -- Andrew J. Kelly wrote: --
> No edition is any more or less stable than any others. It is mainly
> features and capacity. Standard edition will do just fine for your needs.
> --
> Andrew J. Kelly SQL MVP
>
> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
> news:8E5E6311-B5DF-4D1E-9797-92DD6413C57C@.microsoft.com...
> > Hari,
> >> Thanks for your advice. However, I have read the page before and without
> any idea. The point of availability is confused me. In fact, the standard
> edition and enterprise edition is no different except?
> >> --Scalability ( useless to us because we only have 1 CPU machine with
> 512MRAM)
> > --Availability/uptime (useless to us because we don't have a standby or
> cluster machine)
> > --Performance (Time is not so critical because we are just using the 6.5
> version now with no complain)
> > --Advanced analysis ( Analysis is not so critical because we are just
> using the 6.5 version now with no complain)
> >> I just concern, is it enterprise edition is more stable? or standard
> edition is easy to down?
> >> Wanchun
> >> -- Hari Prasad wrote: --
> >> Hi,
> >> Based on your configurations and settings I will recommend you to go
> for SQL
> > Server standard edition.
> >> Have a look into the below link in choosing the edition of sql
> server:-
> >> http://www.microsoft.com/sql/techinfo/planning/SQLReskChooseEd.asp
> >> Thanks
> > Hari
> > MCDBA
> >> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
> > news:08540023-9C99-4569-9A26-F765151912A2@.microsoft.com...
> >> We want to select the edition between standard and enterprise. Our
> usage:
> >> 1) 10 users/application connect to the server at the same time
> >> 2) 5000 row insert per day
> >> 3) Our machine is only 1CPU 2.6GHz and 512 MB RAM with window 2000
> server
> >> 4) One database will be installed
> >> 5) The size of the database around 10GB
> >> Because we want to replace the existing SQL6.5 with 400MHz 256MRAM
> > database server.
> >> Please advise. Thanks
> >>|||Tibor
My concern is how to prevent the SQL server that increase the memory usage continuously? Or We need to reboot the machine periodically? Please advise
Wanchu
-- Tibor Karaszi wrote: --
Enterprise edition has some distinct features that SE doesn't. You find them at
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_ts_1cdv.as
As for memory, please read below
INF: SQL Server Memory Usag
http://support.microsoft.com/default.aspx?scid=kb;en-us;q32136
http://www.mssqlserver.com/faq/troubleshooting-memoryleak.as
--
Tibor Karaszi, SQL Server MV
http://www.karaszi.com/sqlserver/default.as
http://www.solidqualitylearning.com
"Wanchun" <anonymous@.discussions.microsoft.com> wrote in messag
news:36E3DDB7-B674-4AFA-8A7C-3B7C1A336E3E@.microsoft.com..
> Andrew
>> That mean from our requirement, standard edition is enough for us
> Also, the memory arrangement is the same between standard and enterprise? I am testing with standar
edition, the memory continue to grow from 10M to 110M after I inserted 3000 records. After I re-boot th
machine, the memory back to 10M..... Is it I need to re-boot the machine every week to prevent the memory t
grow' Or enterprise edition can handle it better
>> Any other Enterprise features that better than Standard
>> Thank
>> -- Andrew J. Kelly wrote: --
>> No edition is any more or less stable than any others. It is mainl
> features and capacity. Standard edition will do just fine for your needs
>> --
> Andrew J. Kelly SQL MV
>> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in messag
> news:8E5E6311-B5DF-4D1E-9797-92DD6413C57C@.microsoft.com..
>> Hari
>> Thanks for your advice. However, I have read the page before and withou
> any idea. The point of availability is confused me. In fact, the standar
> edition and enterprise edition is no different except
>> --Scalability ( useless to us because we only have 1 CPU machine wit
> 512MRAM
>> --Availability/uptime (useless to us because we don't have a standby o
> cluster machine
>> --Performance (Time is not so critical because we are just using the 6.
> version now with no complain
>> --Advanced analysis ( Analysis is not so critical because we are jus
> using the 6.5 version now with no complain
>> I just concern, is it enterprise edition is more stable? or standar
> edition is easy to down
>> Wanchu
>> -- Hari Prasad wrote: --
>> Hi
>> Based on your configurations and settings I will recommend you to g
> for SQ
>> Server standard edition
>> Have a look into the below link in choosing the edition of sq
> server:
>> http://www.microsoft.com/sql/techinfo/planning/SQLReskChooseEd.as
>> Thank
>> Har
>> MCDB
>> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in messag
>> news:08540023-9C99-4569-9A26-F765151912A2@.microsoft.com..
>> We want to select the edition between standard and enterprise. Ou
> usage
>> 1) 10 users/application connect to the server at the same tim
>> 2) 5000 row insert per da
>> 3) Our machine is only 1CPU 2.6GHz and 512 MB RAM with window 200
> serve
>> 4) One database will be installe
>> 5) The size of the database around 10G
>> Because we want to replace the existing SQL6.5 with 400MHz 256MRA
>> database server
>> Please advise. Thank
>>|||Please read the links I posted about memory allocation algorithms in SQL Server. This is normal, and no reboot
is necessary.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
news:DF073FD2-4A17-4122-BCEC-E9FB5E5AF5EF@.microsoft.com...
> Tibor,
> My concern is how to prevent the SQL server that increase the memory usage continuously? Or We need to
reboot the machine periodically? Please advise.
> Wanchun
> -- Tibor Karaszi wrote: --
> Enterprise edition has some distinct features that SE doesn't. You find them at:
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_ts_1cdv.asp
> As for memory, please read below:
> INF: SQL Server Memory Usage
> http://support.microsoft.com/default.aspx?scid=kb;en-us;q321363
> http://www.mssqlserver.com/faq/troubleshooting-memoryleak.asp
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
> news:36E3DDB7-B674-4AFA-8A7C-3B7C1A336E3E@.microsoft.com...
> > Andrew,
> >> That mean from our requirement, standard edition is enough for us?
> > Also, the memory arrangement is the same between standard and enterprise? I am testing with standard
> edition, the memory continue to grow from 10M to 110M after I inserted 3000 records. After I re-boot
the
> machine, the memory back to 10M..... Is it I need to re-boot the machine every week to prevent the
memory to
> grow' Or enterprise edition can handle it better?
> >> Any other Enterprise features that better than Standard?
> >> Thanks
> >> -- Andrew J. Kelly wrote: --
> >> No edition is any more or less stable than any others. It is mainly
> > features and capacity. Standard edition will do just fine for your needs.
> >> --
> > Andrew J. Kelly SQL MVP
> >> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
> > news:8E5E6311-B5DF-4D1E-9797-92DD6413C57C@.microsoft.com...
> >> Hari,
> >> Thanks for your advice. However, I have read the page before and without
> > any idea. The point of availability is confused me. In fact, the standard
> > edition and enterprise edition is no different except?
> >> --Scalability ( useless to us because we only have 1 CPU machine with
> > 512MRAM)
> >> --Availability/uptime (useless to us because we don't have a standby or
> > cluster machine)
> >> --Performance (Time is not so critical because we are just using the 6.5
> > version now with no complain)
> >> --Advanced analysis ( Analysis is not so critical because we are just
> > using the 6.5 version now with no complain)
> >> I just concern, is it enterprise edition is more stable? or standard
> > edition is easy to down?
> >> Wanchun
> >> -- Hari Prasad wrote: --
> >> Hi,
> >> Based on your configurations and settings I will recommend you to go
> > for SQL
> >> Server standard edition.
> >> Have a look into the below link in choosing the edition of sql
> > server:-
> >> http://www.microsoft.com/sql/techinfo/planning/SQLReskChooseEd.asp
> >> Thanks
> >> Hari
> >> MCDBA
> >> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
> >> news:08540023-9C99-4569-9A26-F765151912A2@.microsoft.com...
> >> We want to select the edition between standard and enterprise. Our
> > usage:
> >> 1) 10 users/application connect to the server at the same time
> >> 2) 5000 row insert per day
> >> 3) Our machine is only 1CPU 2.6GHz and 512 MB RAM with window 2000
> > server
> >> 4) One database will be installed
> >> 5) The size of the database around 10GB
> >> Because we want to replace the existing SQL6.5 with 400MHz 256MRAM
> >> database server.
> >> Please advise. Thanks
> >>|||As Tibor points out that is normal behavior and will be the same for both
Std and EE.
Andrew J. Kelly SQL MVP
"Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
news:DF073FD2-4A17-4122-BCEC-E9FB5E5AF5EF@.microsoft.com...
> Tibor,
> My concern is how to prevent the SQL server that increase the memory
usage continuously? Or We need to reboot the machine periodically? Please
advise.
> Wanchun
> -- Tibor Karaszi wrote: --
> Enterprise edition has some distinct features that SE doesn't. You
find them at:
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_ts_1cdv.asp
> As for memory, please read below:
> INF: SQL Server Memory Usage
> http://support.microsoft.com/default.aspx?scid=kb;en-us;q321363
> http://www.mssqlserver.com/faq/troubleshooting-memoryleak.asp
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
> news:36E3DDB7-B674-4AFA-8A7C-3B7C1A336E3E@.microsoft.com...
> > Andrew,
> >> That mean from our requirement, standard edition is enough for us?
> > Also, the memory arrangement is the same between standard and
enterprise? I am testing with standard
> edition, the memory continue to grow from 10M to 110M after I
inserted 3000 records. After I re-boot the
> machine, the memory back to 10M..... Is it I need to re-boot the
machine every week to prevent the memory to
> grow' Or enterprise edition can handle it better?
> >> Any other Enterprise features that better than Standard?
> >> Thanks
> >> -- Andrew J. Kelly wrote: --
> >> No edition is any more or less stable than any others. It is
mainly
> > features and capacity. Standard edition will do just fine for
your needs.
> >> --
> > Andrew J. Kelly SQL MVP
> >> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in
message
> > news:8E5E6311-B5DF-4D1E-9797-92DD6413C57C@.microsoft.com...
> >> Hari,
> >> Thanks for your advice. However, I have read the page before and
without
> > any idea. The point of availability is confused me. In fact,
the standard
> > edition and enterprise edition is no different except?
> >> --Scalability ( useless to us because we only have 1 CPU machine
with
> > 512MRAM)
> >> --Availability/uptime (useless to us because we don't have a
standby or
> > cluster machine)
> >> --Performance (Time is not so critical because we are just using
the 6.5
> > version now with no complain)
> >> --Advanced analysis ( Analysis is not so critical because we are
just
> > using the 6.5 version now with no complain)
> >> I just concern, is it enterprise edition is more stable? or
standard
> > edition is easy to down?
> >> Wanchun
> >> -- Hari Prasad wrote: --
> >> Hi,
> >> Based on your configurations and settings I will recommend
you to go
> > for SQL
> >> Server standard edition.
> >> Have a look into the below link in choosing the edition of
sql
> > server:-
> >>
http://www.microsoft.com/sql/techinfo/planning/SQLReskChooseEd.asp
> >> Thanks
> >> Hari
> >> MCDBA
> >> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in
message
> >> news:08540023-9C99-4569-9A26-F765151912A2@.microsoft.com...
> >> We want to select the edition between standard and enterprise.
Our
> > usage:
> >> 1) 10 users/application connect to the server at the same time
> >> 2) 5000 row insert per day
> >> 3) Our machine is only 1CPU 2.6GHz and 512 MB RAM with window
2000
> > server
> >> 4) One database will be installed
> >> 5) The size of the database around 10GB
> >> Because we want to replace the existing SQL6.5 with 400MHz
256MRAM
> >> database server.
> >> Please advise. Thanks
> >>|||Thanks again Tibor, however, if SQL used all the physical memory of the machine, then the SQL can still run smoothly? or better reboot the machine
Wanchu
-- Tibor Karaszi wrote: --
Please read the links I posted about memory allocation algorithms in SQL Server. This is normal, and no reboo
is necessary
--
Tibor Karaszi, SQL Server MV
http://www.karaszi.com/sqlserver/default.as
http://www.solidqualitylearning.com
"Wanchun" <anonymous@.discussions.microsoft.com> wrote in messag
news:DF073FD2-4A17-4122-BCEC-E9FB5E5AF5EF@.microsoft.com..
> Tibor
> My concern is how to prevent the SQL server that increase the memory usage continuously? Or We need t
reboot the machine periodically? Please advise
>> Wanchu
>> -- Tibor Karaszi wrote: --
>> Enterprise edition has some distinct features that SE doesn't. You find them at
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_ts_1cdv.as
>> As for memory, please read below
>> INF: SQL Server Memory Usag
> http://support.microsoft.com/default.aspx?scid=kb;en-us;q32136
>> http://www.mssqlserver.com/faq/troubleshooting-memoryleak.as
>> --
> Tibor Karaszi, SQL Server MV
> http://www.karaszi.com/sqlserver/default.as
> http://www.solidqualitylearning.com
>> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in messag
> news:36E3DDB7-B674-4AFA-8A7C-3B7C1A336E3E@.microsoft.com..
>> Andrew
>> That mean from our requirement, standard edition is enough for us
>> Also, the memory arrangement is the same between standard and enterprise? I am testing with standar
> edition, the memory continue to grow from 10M to 110M after I inserted 3000 records. After I re-boo
th
> machine, the memory back to 10M..... Is it I need to re-boot the machine every week to prevent th
memory t
> grow' Or enterprise edition can handle it better
>> Any other Enterprise features that better than Standard
>> Thank
>>> -- Andrew J. Kelly wrote: --
>> No edition is any more or less stable than any others. It is mainl
>> features and capacity. Standard edition will do just fine for your needs
>> --
>> Andrew J. Kelly SQL MV
>> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in messag
>> news:8E5E6311-B5DF-4D1E-9797-92DD6413C57C@.microsoft.com..
>> Hari
>> Thanks for your advice. However, I have read the page before and withou
>> any idea. The point of availability is confused me. In fact, the standar
>> edition and enterprise edition is no different except
>> --Scalability ( useless to us because we only have 1 CPU machine wit
>> 512MRAM
>> --Availability/uptime (useless to us because we don't have a standby o
>> cluster machine
>> --Performance (Time is not so critical because we are just using the 6.
>> version now with no complain
>> --Advanced analysis ( Analysis is not so critical because we are jus
>> using the 6.5 version now with no complain
>> I just concern, is it enterprise edition is more stable? or standar
>> edition is easy to down
>> Wanchu
>> -- Hari Prasad wrote: --
>> Hi
>> Based on your configurations and settings I will recommend you to g
>> for SQ
>> Server standard edition
>> Have a look into the below link in choosing the edition of sq
>> server:
>> http://www.microsoft.com/sql/techinfo/planning/SQLReskChooseEd.as
>> Thank
>> Har
>> MCDB
>> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in messag
>> news:08540023-9C99-4569-9A26-F765151912A2@.microsoft.com..
>> We want to select the edition between standard and enterprise. Our
>> usage:
>> 1) 10 users/application connect to the server at the same time
>> 2) 5000 row insert per day
>> 3) Our machine is only 1CPU 2.6GHz and 512 MB RAM with window 2000
>> server
>> 4) One database will be installed
>> 5) The size of the database around 10GB
>> Because we want to replace the existing SQL6.5 with 400MHz 256MRAM
>> database server.
>> Please advise. Thanks
>>|||The purpose if buying memory is for it to be used. SQL Server does just that. Yes, it is normal for a SQL
Server installation to see all memory being used. :-)
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Wanhcun" <anonymous@.discussions.microsoft.com> wrote in message
news:70CBBAD5-7E54-4EB8-9A9C-3EBDEBF2A674@.microsoft.com...
> Thanks again Tibor, however, if SQL used all the physical memory of the machine, then the SQL can still run
smoothly? or better reboot the machine?
> Wanchun
> -- Tibor Karaszi wrote: --
> Please read the links I posted about memory allocation algorithms in SQL Server. This is normal, and no
reboot
> is necessary.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
> news:DF073FD2-4A17-4122-BCEC-E9FB5E5AF5EF@.microsoft.com...
> > Tibor,
> > My concern is how to prevent the SQL server that increase the memory usage continuously? Or We
need to
> reboot the machine periodically? Please advise.
> >> Wanchun
> >> -- Tibor Karaszi wrote: --
> >> Enterprise edition has some distinct features that SE doesn't. You find them at:
> > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_ts_1cdv.asp
> >> As for memory, please read below:
> >> INF: SQL Server Memory Usage
> > http://support.microsoft.com/default.aspx?scid=kb;en-us;q321363
> >> http://www.mssqlserver.com/faq/troubleshooting-memoryleak.asp
> >> --
> > Tibor Karaszi, SQL Server MVP
> > http://www.karaszi.com/sqlserver/default.asp
> > http://www.solidqualitylearning.com/
> >> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
> > news:36E3DDB7-B674-4AFA-8A7C-3B7C1A336E3E@.microsoft.com...
> >> Andrew,
> >> That mean from our requirement, standard edition is enough for us?
> >> Also, the memory arrangement is the same between standard and enterprise? I am testing with standard
> > edition, the memory continue to grow from 10M to 110M after I inserted 3000 records. After I
re-boot
> the
> > machine, the memory back to 10M..... Is it I need to re-boot the machine every week to prevent
the
> memory to
> > grow' Or enterprise edition can handle it better?
> >> Any other Enterprise features that better than Standard?
> >> Thanks
> >>> -- Andrew J. Kelly wrote: --
> >> No edition is any more or less stable than any others. It is mainly
> >> features and capacity. Standard edition will do just fine for your needs.
> >> --
> >> Andrew J. Kelly SQL MVP
> >> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
> >> news:8E5E6311-B5DF-4D1E-9797-92DD6413C57C@.microsoft.com...
> >> Hari,
> >> Thanks for your advice. However, I have read the page before and without
> >> any idea. The point of availability is confused me. In fact, the standard
> >> edition and enterprise edition is no different except?
> >> --Scalability ( useless to us because we only have 1 CPU machine with
> >> 512MRAM)
> >> --Availability/uptime (useless to us because we don't have a standby or
> >> cluster machine)
> >> --Performance (Time is not so critical because we are just using the 6.5
> >> version now with no complain)
> >> --Advanced analysis ( Analysis is not so critical because we are just
> >> using the 6.5 version now with no complain)
> >> I just concern, is it enterprise edition is more stable? or standard
> >> edition is easy to down?
> >> Wanchun
> >> -- Hari Prasad wrote: --
> >> Hi,
> >> Based on your configurations and settings I will recommend you to go
> >> for SQL
> >> Server standard edition.
> >> Have a look into the below link in choosing the edition of sql
> >> server:-
> >> http://www.microsoft.com/sql/techinfo/planning/SQLReskChooseEd.asp
> >> Thanks
> >> Hari
> >> MCDBA
> >> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
> >> news:08540023-9C99-4569-9A26-F765151912A2@.microsoft.com...
> >> We want to select the edition between standard and enterprise. Our
> >> usage:
> >> 1) 10 users/application connect to the server at the same time
> >> 2) 5000 row insert per day
> >> 3) Our machine is only 1CPU 2.6GHz and 512 MB RAM with window 2000
> >> server
> >> 4) One database will be installed
> >> 5) The size of the database around 10GB
> >> Because we want to replace the existing SQL6.5 with 400MHz 256MRAM
> >> database server.
> >> Please advise. Thanks
> >>|||Tibor
This is because my machine only contain 512 MRAM... then we need to set the "maximun memory" of SQL server around 400M and let 100M memory that can be used by the OS? Please advise.Thanks...
Regards
Wanchu
-- Tibor Karaszi wrote: --
The purpose if buying memory is for it to be used. SQL Server does just that. Yes, it is normal for a SQ
Server installation to see all memory being used. :-
--
Tibor Karaszi, SQL Server MV
http://www.karaszi.com/sqlserver/default.as
http://www.solidqualitylearning.com
"Wanhcun" <anonymous@.discussions.microsoft.com> wrote in messag
news:70CBBAD5-7E54-4EB8-9A9C-3EBDEBF2A674@.microsoft.com..
> Thanks again Tibor, however, if SQL used all the physical memory of the machine, then the SQL can still ru
smoothly? or better reboot the machine
>> Wanchu
>> -- Tibor Karaszi wrote: --
>> Please read the links I posted about memory allocation algorithms in SQL Server. This is normal, and n
reboo
> is necessary
>> --
> Tibor Karaszi, SQL Server MV
> http://www.karaszi.com/sqlserver/default.as
> http://www.solidqualitylearning.com
>> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in messag
> news:DF073FD2-4A17-4122-BCEC-E9FB5E5AF5EF@.microsoft.com..
>> Tibor
>> My concern is how to prevent the SQL server that increase the memory usage continuously? Or W
need t
> reboot the machine periodically? Please advise
>> Wanchu
>> -- Tibor Karaszi wrote: --
>> Enterprise edition has some distinct features that SE doesn't. You find them at
>> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_ts_1cdv.as
>> As for memory, please read below
>> INF: SQL Server Memory Usag
>> http://support.microsoft.com/default.aspx?scid=kb;en-us;q32136
>> http://www.mssqlserver.com/faq/troubleshooting-memoryleak.as
>> --
>> Tibor Karaszi, SQL Server MV
>> http://www.karaszi.com/sqlserver/default.as
>> http://www.solidqualitylearning.com
>> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in messag
>> news:36E3DDB7-B674-4AFA-8A7C-3B7C1A336E3E@.microsoft.com..
>> Andrew
>> That mean from our requirement, standard edition is enough for us
>> Also, the memory arrangement is the same between standard and enterprise? I am testing with standar
>> edition, the memory continue to grow from 10M to 110M after I inserted 3000 records. After
re-boo
> th
>> machine, the memory back to 10M..... Is it I need to re-boot the machine every week to preven
th
> memory t
>> grow' Or enterprise edition can handle it better
>> Any other Enterprise features that better than Standard
>> Thank
>>> -- Andrew J. Kelly wrote: --
>> No edition is any more or less stable than any others. It is mainl
>> features and capacity. Standard edition will do just fine for your needs
>> --
>> Andrew J. Kelly SQL MV
>> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in messag
>> news:8E5E6311-B5DF-4D1E-9797-92DD6413C57C@.microsoft.com..
>> Hari
>> Thanks for your advice. However, I have read the page before and withou
>> any idea. The point of availability is confused me. In fact, the standar
>> edition and enterprise edition is no different except
>> --Scalability ( useless to us because we only have 1 CPU machine wit
>> 512MRAM
>> --Availability/uptime (useless to us because we don't have a standby o
>> cluster machine
>> --Performance (Time is not so critical because we are just using the 6.
>> version now with no complain
>> --Advanced analysis ( Analysis is not so critical because we are just
>> using the 6.5 version now with no complain)
>> I just concern, is it enterprise edition is more stable? or standard
>> edition is easy to down?
>> Wanchun
>> -- Hari Prasad wrote: --
>> Hi,
>> Based on your configurations and settings I will recommend you to go
>> for SQL
>> Server standard edition.
>> Have a look into the below link in choosing the edition of sql
>> server:-
>> http://www.microsoft.com/sql/techinfo/planning/SQLReskChooseEd.asp
>> Thanks
>> Hari
>> MCDBA
>>> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
>> news:08540023-9C99-4569-9A26-F765151912A2@.microsoft.com...
>> We want to select the edition between standard and enterprise. Our
>> usage:
>> 1) 10 users/application connect to the server at the same time
>> 2) 5000 row insert per day
>> 3) Our machine is only 1CPU 2.6GHz and 512 MB RAM with window 2000
>> server
>> 4) One database will be installed
>> 5) The size of the database around 10GB
>> Because we want to replace the existing SQL6.5 with 400MHz 256MRAM
>> database server.
>> Please advise. Thanks
>>|||The fact that you only have 512 MB doesn't change the memory allocation algorithms. SQL Server will use the
memory in the machine (but of course leave space for OS and a little bit more). But sure, you can set a max if
you absolutely want to...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
news:3D73FA4A-D85C-40BF-BC30-D2F32E57602B@.microsoft.com...
> Tibor,
> This is because my machine only contain 512 MRAM... then we need to set the "maximun memory" of SQL server
around 400M and let 100M memory that can be used by the OS? Please advise.Thanks....
> Regards,
> Wanchun
> -- Tibor Karaszi wrote: --
> The purpose if buying memory is for it to be used. SQL Server does just that. Yes, it is normal for a
SQL
> Server installation to see all memory being used. :-)
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Wanhcun" <anonymous@.discussions.microsoft.com> wrote in message
> news:70CBBAD5-7E54-4EB8-9A9C-3EBDEBF2A674@.microsoft.com...
> > Thanks again Tibor, however, if SQL used all the physical memory of the machine, then the SQL can
still run
> smoothly? or better reboot the machine?
> >> Wanchun
> >> -- Tibor Karaszi wrote: --
> >> Please read the links I posted about memory allocation algorithms in SQL Server. This is
normal, and no
> reboot
> > is necessary.
> >> --
> > Tibor Karaszi, SQL Server MVP
> > http://www.karaszi.com/sqlserver/default.asp
> > http://www.solidqualitylearning.com/
> >> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
> > news:DF073FD2-4A17-4122-BCEC-E9FB5E5AF5EF@.microsoft.com...
> >> Tibor,
> >> My concern is how to prevent the SQL server that increase the memory usage continuously? Or We
> need to
> > reboot the machine periodically? Please advise.
> >> Wanchun
> >> -- Tibor Karaszi wrote: --
> >> Enterprise edition has some distinct features that SE doesn't. You find them at:
> >> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_ts_1cdv.asp
> >> As for memory, please read below:
> >> INF: SQL Server Memory Usage
> >> http://support.microsoft.com/default.aspx?scid=kb;en-us;q321363
> >> http://www.mssqlserver.com/faq/troubleshooting-memoryleak.asp
> >> --
> >> Tibor Karaszi, SQL Server MVP
> >> http://www.karaszi.com/sqlserver/default.asp
> >> http://www.solidqualitylearning.com/
> >> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
> >> news:36E3DDB7-B674-4AFA-8A7C-3B7C1A336E3E@.microsoft.com...
> >> Andrew,
> >> That mean from our requirement, standard edition is enough for us?
> >> Also, the memory arrangement is the same between standard and enterprise? I am testing with
standard
> >> edition, the memory continue to grow from 10M to 110M after I inserted 3000 records. After I
> re-boot
> > the
> >> machine, the memory back to 10M..... Is it I need to re-boot the machine every week to prevent
> the
> > memory to
> >> grow' Or enterprise edition can handle it better?
> >> Any other Enterprise features that better than Standard?
> >> Thanks
> >>> -- Andrew J. Kelly wrote: --
> >> No edition is any more or less stable than any others. It is mainly
> >> features and capacity. Standard edition will do just fine for your needs.
> >> --
> >> Andrew J. Kelly SQL MVP
> >> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
> >> news:8E5E6311-B5DF-4D1E-9797-92DD6413C57C@.microsoft.com...
> >> Hari,
> >> Thanks for your advice. However, I have read the page before and without
> >> any idea. The point of availability is confused me. In fact, the standard
> >> edition and enterprise edition is no different except?
> >> --Scalability ( useless to us because we only have 1 CPU machine with
> >> 512MRAM)
> >> --Availability/uptime (useless to us because we don't have a standby or
> >> cluster machine)
> >> --Performance (Time is not so critical because we are just using the 6.5
> >> version now with no complain)
> >> --Advanced analysis ( Analysis is not so critical because we are just
> >> using the 6.5 version now with no complain)
> >> I just concern, is it enterprise edition is more stable? or standard
> >> edition is easy to down?
> >> Wanchun
> >> -- Hari Prasad wrote: --
> >> Hi,
> >> Based on your configurations and settings I will recommend you to go
> >> for SQL
> >> Server standard edition.
> >> Have a look into the below link in choosing the edition of sql
> >> server:-
> >> http://www.microsoft.com/sql/techinfo/planning/SQLReskChooseEd.asp
> >> Thanks
> >> Hari
> >> MCDBA
> >>> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
> >> news:08540023-9C99-4569-9A26-F765151912A2@.microsoft.com...
> >> We want to select the edition between standard and enterprise. Our
> >> usage:
> >> 1) 10 users/application connect to the server at the same time
> >> 2) 5000 row insert per day
> >> 3) Our machine is only 1CPU 2.6GHz and 512 MB RAM with window 2000
> >> server
> >> 4) One database will be installed
> >> 5) The size of the database around 10GB
> >> Because we want to replace the existing SQL6.5 with 400MHz 256MRAM
> >> database server.
> >> Please advise. Thanks
> >>|||The max memory only sets an upper limit for the memory pool. There is an
area called the mem to leave that gets allocated first. By default it can
use to to 256MB so if you set the max memory to 400 you will most likely
still swap with the OS. While it may be better than not changing anything I
would set it even lower. You stated you only do 5000 inserts a day so you
should not require a lot of memory to operate properly. Try setting it to
300MB and see if that helps. Memory is cheap these days and you might want
to look into adding more later on.
--
Andrew J. Kelly SQL MVP
"Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
news:3D73FA4A-D85C-40BF-BC30-D2F32E57602B@.microsoft.com...
> Tibor,
> This is because my machine only contain 512 MRAM... then we need to set
the "maximun memory" of SQL server around 400M and let 100M memory that can
be used by the OS? Please advise.Thanks....
> Regards,
> Wanchun
> -- Tibor Karaszi wrote: --
> The purpose if buying memory is for it to be used. SQL Server does
just that. Yes, it is normal for a SQL
> Server installation to see all memory being used. :-)
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Wanhcun" <anonymous@.discussions.microsoft.com> wrote in message
> news:70CBBAD5-7E54-4EB8-9A9C-3EBDEBF2A674@.microsoft.com...
> > Thanks again Tibor, however, if SQL used all the physical memory of
the machine, then the SQL can still run
> smoothly? or better reboot the machine?
> >> Wanchun
> >> -- Tibor Karaszi wrote: --
> >> Please read the links I posted about memory allocation
algorithms in SQL Server. This is normal, and no
> reboot
> > is necessary.
> >> --
> > Tibor Karaszi, SQL Server MVP
> > http://www.karaszi.com/sqlserver/default.asp
> > http://www.solidqualitylearning.com/
> >> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in
message
> > news:DF073FD2-4A17-4122-BCEC-E9FB5E5AF5EF@.microsoft.com...
> >> Tibor,
> >> My concern is how to prevent the SQL server that increase the
memory usage continuously? Or We
> need to
> > reboot the machine periodically? Please advise.
> >> Wanchun
> >> -- Tibor Karaszi wrote: --
> >> Enterprise edition has some distinct features that SE
doesn't. You find them at:
> >>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_ts_1cdv.asp
> >> As for memory, please read below:
> >> INF: SQL Server Memory Usage
> >>
http://support.microsoft.com/default.aspx?scid=kb;en-us;q321363
> >>
http://www.mssqlserver.com/faq/troubleshooting-memoryleak.asp
> >> --
> >> Tibor Karaszi, SQL Server MVP
> >> http://www.karaszi.com/sqlserver/default.asp
> >> http://www.solidqualitylearning.com/
> >> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in
message
> >> news:36E3DDB7-B674-4AFA-8A7C-3B7C1A336E3E@.microsoft.com...
> >> Andrew,
> >> That mean from our requirement, standard edition is enough for
us?
> >> Also, the memory arrangement is the same between standard and
enterprise? I am testing with standard
> >> edition, the memory continue to grow from 10M to 110M after I
inserted 3000 records. After I
> re-boot
> > the
> >> machine, the memory back to 10M..... Is it I need to re-boot
the machine every week to prevent
> the
> > memory to
> >> grow' Or enterprise edition can handle it better?
> >> Any other Enterprise features that better than Standard?
> >> Thanks
> >>> -- Andrew J. Kelly wrote: --
> >> No edition is any more or less stable than any others. It
is mainly
> >> features and capacity. Standard edition will do just fine
for your needs.
> >> --
> >> Andrew J. Kelly SQL MVP
> >> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in
message
> >> news:8E5E6311-B5DF-4D1E-9797-92DD6413C57C@.microsoft.com...
> >> Hari,
> >> Thanks for your advice. However, I have read the page before
and without
> >> any idea. The point of availability is confused me. In fact,
the standard
> >> edition and enterprise edition is no different except?
> >> --Scalability ( useless to us because we only have 1 CPU
machine with
> >> 512MRAM)
> >> --Availability/uptime (useless to us because we don't have a
standby or
> >> cluster machine)
> >> --Performance (Time is not so critical because we are just using
the 6.5
> >> version now with no complain)
> >> --Advanced analysis ( Analysis is not so critical because we are
just
> >> using the 6.5 version now with no complain)
> >> I just concern, is it enterprise edition is more stable? or
standard
> >> edition is easy to down?
> >> Wanchun
> >> -- Hari Prasad wrote: --
> >> Hi,
> >> Based on your configurations and settings I will recommend
you to go
> >> for SQL
> >> Server standard edition.
> >> Have a look into the below link in choosing the edition of
sql
> >> server:-
> >>
http://www.microsoft.com/sql/techinfo/planning/SQLReskChooseEd.asp
> >> Thanks
> >> Hari
> >> MCDBA
> >>> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in
message
> >> news:08540023-9C99-4569-9A26-F765151912A2@.microsoft.com...
> >> We want to select the edition between standard and enterprise.
Our
> >> usage:
> >> 1) 10 users/application connect to the server at the same time
> >> 2) 5000 row insert per day
> >> 3) Our machine is only 1CPU 2.6GHz and 512 MB RAM with window
2000
> >> server
> >> 4) One database will be installed
> >> 5) The size of the database around 10GB
> >> Because we want to replace the existing SQL6.5 with 400MHz
256MRAM
> >> database server.
> >> Please advise. Thanks
> >>
Subscribe to:
Posts (Atom)