Dan,
Thank you. That is the way I have always configured any SQL server I have installed.
I just wanted to make sure Vantage had no specific reason for the configuration we have.
Thanks,
Darren
PACE, Incorporated
Information Systems
----- Original Message ----
From: propel6919 <propel6919@...>
To: vantage@yahoogroups.com
Sent: Monday, June 25, 2007 9:01:14 PM
Subject: [Vantage] Re: Vantage 8_11b SQL Database config
Below is the way I see most SQL installs configured
1. Recovery model is full to allow for maximum data recovery and
other benefits.
2. Pre-allocate as much space as you can to the data files and the
log files should be preset at about 25% of the data files. Autogrow
is ok if you know how often your database is doing this. By setting
the file sizes to a larger size reduces the ongoing fragmentation
that autogrowing all the time can cause this increasing performance
3. Turn off auto shrink unless there are space concerns
Just a few ways that I have seen SQL configured.
Dan
--- In vantage@yahoogroups .com, "scubadoobydootoo"
<scubadoobydootoo@ ...> wrote:
Boardwalk for $500? In 2007? Ha! Play Monopoly Here and Now (it's updated for today's economy) at Yahoo! Games.
http://get.games.yahoo.com/proddesc?gamekey=monopolyherenow
[Non-text portions of this message have been removed]
Thank you. That is the way I have always configured any SQL server I have installed.
I just wanted to make sure Vantage had no specific reason for the configuration we have.
Thanks,
Darren
PACE, Incorporated
Information Systems
----- Original Message ----
From: propel6919 <propel6919@...>
To: vantage@yahoogroups.com
Sent: Monday, June 25, 2007 9:01:14 PM
Subject: [Vantage] Re: Vantage 8_11b SQL Database config
Below is the way I see most SQL installs configured
1. Recovery model is full to allow for maximum data recovery and
other benefits.
2. Pre-allocate as much space as you can to the data files and the
log files should be preset at about 25% of the data files. Autogrow
is ok if you know how often your database is doing this. By setting
the file sizes to a larger size reduces the ongoing fragmentation
that autogrowing all the time can cause this increasing performance
3. Turn off auto shrink unless there are space concerns
Just a few ways that I have seen SQL configured.
Dan
--- In vantage@yahoogroups .com, "scubadoobydootoo"
<scubadoobydootoo@ ...> wrote:
>3.9GB
> I was wondering how people have their SQL Databases configured.
> Our Database is in Simple Mode, the MfgSys80 is a little under
> and space allocated is 180mb log file is set at 16mb Autogrow isset at
> 10% and AutoShrink is enabled. I've never really seen a SQLdatabase
> configured this way but have been told that it is the way Epicorwanted
> it installed, so I am curious how some other installations areerror
> configured.
>
> I have been working with Epicor and Microsoft on an on going 4GL
> on our system, it started the first day of going live in January. Iserver
> didn't start until a few months later, so I have inherited the
> pre-configured. This is the second server that has been installedand
> the problem didn't go away, so I want to see if someone has thesame
> database configuration but doesn't have the error.____________________________________________________________________________________
>
> Thank you,
> Darren
> PACE, Incorporated
> Information Systems
>
Boardwalk for $500? In 2007? Ha! Play Monopoly Here and Now (it's updated for today's economy) at Yahoo! Games.
http://get.games.yahoo.com/proddesc?gamekey=monopolyherenow
[Non-text portions of this message have been removed]