Showing posts with label file. Show all posts
Showing posts with label file. Show all posts

Wednesday, March 28, 2012

performance differences between queries...

I am updating a db with data from a file, in this data we have new info, info that has been updated and info that is to be removed from the db.
Now I was wondering which approach results in better performance/shorter executin time:

1. first update excisting values, then insert new ones, and last delete cancelled data

or

2. delete cancelled data and data that will be updated, then insert new and updated info

I get all this data from a file, in that file all rows are similar and there is one column that defines if the data is new, updated or to be deleted (thus all the updates also include the information for the enty that has not been altered).

// PatiPati, I think there are too many unknown variables to properly answer the question. For instance, how many columns are you updating compared to how many columns are not being updated? If you're updating one small column, and there are ten large columns, say Char(255), that are not being updated, then I believe an update would be faster than a "delete and insert all new rows". However, you would have to have the index to support finding the rows that need updating.

Personally, I always choose the way that makes the most sense logically. I would delete cancelled data, then update existing data and then insert the new rows.

Roby2222|||Thanks for you answer Roby2222, I hope this additional info will clarify things.

The amount of columns that are being updated differs from time to time, sometimes there is just one column that needs updating and sometimes almost all columns have to be updated...

Most columns are about the same size 'cause their max size is predefined in the system where it originates from.

Basically I was just wondering if it is worth doing 3 steps (delete+update+insert) when you get the same result with 2 steps (delet+insert)?

Pati|||Pati,

If you're doing a bulk insert, then the two step process will usually be quicker. If you're inserting row by row, then it's probably a toss up. If you really want to know the exact answer for your particular situation, I would run a test and benchmark both methods. You can use one scripts with all of the necessary statements, and then not how long it took to run in query analyzer.

Hope this helps,
Roby2222|||Thanks for your answers!

I think I'll go for the 2 step solution, 'cause it will probably result in simpler code (and therefore easier for someone else to read later if neccessary).

Perhaps I'll also test the performance manually as you suggested sometime later on when I'll have some time to spare! :)

Pati

Friday, March 23, 2012

Performance Counter Problems

Hi,
We are running SQL Server 2000 SP3a on Windows 2003 Server.
I use the Performance Log to capture some performance counters and saved
as text file. When I opened the captured file, I discovered that the
SQLServer Counters are not recording anything (\SQLServer:Memory
manager, \SQLServer:Buffer manager, etc ) But other counters like
\Physical Disk: %Disk Time, \Processor:%Processor Time are recording
values.
I will appreciate your help.
Thanks
Egbon
*** Sent via Developersdex http://www.examnotes.net ***
Don't just participate in USENET...get rewarded for it!"Egbon V." <vnjowusi@.gosps.com> wrote in message
news:eXySJtO7DHA.2656@.TK2MSFTNGP11.phx.gbl...
> We are running SQL Server 2000 SP3a on Windows 2003 Server.
> I use the Performance Log to capture some performance counters and saved
> as text file. When I opened the captured file, I discovered that the
> SQLServer Counters are not recording anything (\SQLServer:Memory
> manager, \SQLServer:Buffer manager, etc ) But other counters like
> \Physical Disk: %Disk Time, \Processor:%Processor Time are recording
> values.
This article looks promising, it may be a WMI registration issue:
http://support.microsoft.com/defaul...0&Product=sql2k
Steve|||Steve,
Thanks a lot!
Egbon
*** Sent via Developersdex http://www.examnotes.net ***
Don't just participate in USENET...get rewarded for it!sql

Tuesday, March 20, 2012

Performance baselines

Hi,
I'm currently looking into moving a table to it's own file group with
a view to improving performance.
I want some way to prove that there is a performance improvement so
want to take a performance base line of current activity to compare to
once I've moved the table. I'm going to use
sys.dm_io_virtual_file_stats to get an over view of what IO has been
taken away from the main file group but would also like to get some
table level stats. The number of times the table is accessed should
not change so I was wondering what table level data is available for
me to show an improvement. That is, if there is an improvement!
Cheers
SimonI think you can do one thing here:
Just note down the time taken(duration) for queries that are getting fired
on this table with existing setup during off peak or peak hours as per ur
envt. and then run them(queries or procedures) again once u r done with
movement and compare the stats.
Manu
"simon.pope.public@.gmail.com" wrote:
> Hi,
> I'm currently looking into moving a table to it's own file group with
> a view to improving performance.
> I want some way to prove that there is a performance improvement so
> want to take a performance base line of current activity to compare to
> once I've moved the table. I'm going to use
> sys.dm_io_virtual_file_stats to get an over view of what IO has been
> taken away from the main file group but would also like to get some
> table level stats. The number of times the table is accessed should
> not change so I was wondering what table level data is available for
> me to show an improvement. That is, if there is an improvement!
> Cheers
> Simon
>|||On 13 Sep, 20:40, manu <m...@.discussions.microsoft.com> wrote:
> I think you can do one thing here:
> Just note down the time taken(duration) for queries that are getting fired
> on this table with existing setup during off peak or peak hours as per ur
> envt. and then run them(queries or procedures) again once u r done with
> movement and compare the stats.
> Manu
>
> "simon.pope.pub...@.gmail.com" wrote:
> > Hi,
> > I'm currently looking into moving a table to it's own file group with
> > a view to improving performance.
> > I want some way to prove that there is a performance improvement so
> > want to take a performance base line of current activity to compare to
> > once I've moved the table. I'm going to use
> > sys.dm_io_virtual_file_stats to get an over view of what IO has been
> > taken away from the main file group but would also like to get some
> > table level stats. The number of times the table is accessed should
> > not change so I was wondering what table level data is available for
> > me to show an improvement. That is, if there is an improvement!
> > Cheers
> > Simon- Hide quoted text -
> - Show quoted text -
Cheers manu, I think you're right. It is a performance enhancement
after all and so time taken to query data in the table is as good an
indicator as any.

PErformance and SQL Server Error Log

I am using SQL 2K.
Size of the SQL Server error log file will degrade the performance of SQL
Server.
I am talking about log file which I cleared using SP_CYCLE_ERRORLOG.
Thanks,
JJ
Recycle more often then. How did you determine that it "degraded"
performance?
bert
|||Sorry,
It was my quetion as whether it will degrade the performance or not?
Thanks,
JJ
"bert" <bertcord@.gmail.com> wrote in message
news:1107297013.482698.267950@.l41g2000cwc.googlegr oups.com...
> Recycle more often then. How did you determine that it "degraded"
> performance?
> bert
>
|||Hi
Not that I have ever found. Output to the log file is appended and is not
read by SQL Server itself.
The bigger issue is how do you view it. A 10Mb log file does take a while to
open in EM (or notepad).
We cycle our error logs on our 400 servers every night. This helps us to
keep the Error log entries by day.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"John Smith" <JJSmith45@.hotmail.com> wrote in message
news:#bkfy5KCFHA.3524@.TK2MSFTNGP15.phx.gbl...
> Sorry,
> It was my quetion as whether it will degrade the performance or not?
> Thanks,
> JJ
> "bert" <bertcord@.gmail.com> wrote in message
> news:1107297013.482698.267950@.l41g2000cwc.googlegr oups.com...
>
|||"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:euXu08KCFHA.1936@.TK2MSFTNGP14.phx.gbl...
> Hi
> Not that I have ever found. Output to the log file is appended and is not
> read by SQL Server itself.
> The bigger issue is how do you view it. A 10Mb log file does take a while
to
> open in EM (or notepad).
> We cycle our error logs on our 400 servers every night. This helps us to
> keep the Error log entries by day.
>
We do it on the first of the month. But same idea.. keep it somewhat
reasonable and have enough "old" ones to troubleshoot problems.
|||Another helpful hint: either by registry key or by using SQLEM, you can
modify the properties of the SQL Error logs to increase the number retained.
We set ours to 32 and recycle at 11:59 PM every night.
Another thing to consider, most of what is output to the SQL Server Error
logs also ends up in the server's Application Event log; so, you might want
to increase the size of that log too.
Finally, if you have your security settings to Audit all logins, both the
SQL Server Error logs and the system's Application Event logs can be
enourmous. We currently only set for failed login attempts.
Sincerely,
Anthony Thomas

"Greg D. Moore (Strider)" <mooregr_deleteth1s@.greenms.com> wrote in message
news:EthMd.26166$ZD1.5393@.twister.nyroc.rr.com...
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:euXu08KCFHA.1936@.TK2MSFTNGP14.phx.gbl...
> Hi
> Not that I have ever found. Output to the log file is appended and is not
> read by SQL Server itself.
> The bigger issue is how do you view it. A 10Mb log file does take a while
to
> open in EM (or notepad).
> We cycle our error logs on our 400 servers every night. This helps us to
> keep the Error log entries by day.
>
We do it on the first of the month. But same idea.. keep it somewhat
reasonable and have enough "old" ones to troubleshoot problems.

PErformance and SQL Server Error Log

I am using SQL 2K.
Size of the SQL Server error log file will degrade the performance of SQL
Server.
I am talking about log file which I cleared using SP_CYCLE_ERRORLOG.
Thanks,
JJRecycle more often then. How did you determine that it "degraded"
performance?
bert|||Sorry,
It was my quetion as whether it will degrade the performance or not?
Thanks,
JJ
"bert" <bertcord@.gmail.com> wrote in message
news:1107297013.482698.267950@.l41g2000cwc.googlegroups.com...
> Recycle more often then. How did you determine that it "degraded"
> performance?
> bert
>|||Hi
Not that I have ever found. Output to the log file is appended and is not
read by SQL Server itself.
The bigger issue is how do you view it. A 10Mb log file does take a while to
open in EM (or notepad).
We cycle our error logs on our 400 servers every night. This helps us to
keep the Error log entries by day.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"John Smith" <JJSmith45@.hotmail.com> wrote in message
news:#bkfy5KCFHA.3524@.TK2MSFTNGP15.phx.gbl...
> Sorry,
> It was my quetion as whether it will degrade the performance or not?
> Thanks,
> JJ
> "bert" <bertcord@.gmail.com> wrote in message
> news:1107297013.482698.267950@.l41g2000cwc.googlegroups.com...
> > Recycle more often then. How did you determine that it "degraded"
> > performance?
> >
> > bert
> >
>|||"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:euXu08KCFHA.1936@.TK2MSFTNGP14.phx.gbl...
> Hi
> Not that I have ever found. Output to the log file is appended and is not
> read by SQL Server itself.
> The bigger issue is how do you view it. A 10Mb log file does take a while
to
> open in EM (or notepad).
> We cycle our error logs on our 400 servers every night. This helps us to
> keep the Error log entries by day.
>
We do it on the first of the month. But same idea.. keep it somewhat
reasonable and have enough "old" ones to troubleshoot problems.|||Another helpful hint: either by registry key or by using SQLEM, you can
modify the properties of the SQL Error logs to increase the number retained.
We set ours to 32 and recycle at 11:59 PM every night.
Another thing to consider, most of what is output to the SQL Server Error
logs also ends up in the server's Application Event log; so, you might want
to increase the size of that log too.
Finally, if you have your security settings to Audit all logins, both the
SQL Server Error logs and the system's Application Event logs can be
enourmous. We currently only set for failed login attempts.
Sincerely,
Anthony Thomas
"Greg D. Moore (Strider)" <mooregr_deleteth1s@.greenms.com> wrote in message
news:EthMd.26166$ZD1.5393@.twister.nyroc.rr.com...
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:euXu08KCFHA.1936@.TK2MSFTNGP14.phx.gbl...
> Hi
> Not that I have ever found. Output to the log file is appended and is not
> read by SQL Server itself.
> The bigger issue is how do you view it. A 10Mb log file does take a while
to
> open in EM (or notepad).
> We cycle our error logs on our 400 servers every night. This helps us to
> keep the Error log entries by day.
>
We do it on the first of the month. But same idea.. keep it somewhat
reasonable and have enough "old" ones to troubleshoot problems.

PErformance and SQL Server Error Log

I am using SQL 2K.
Size of the SQL Server error log file will degrade the performance of SQL
Server.
I am talking about log file which I cleared using SP_CYCLE_ERRORLOG.
Thanks,
JJRecycle more often then. How did you determine that it "degraded"
performance?
bert|||Sorry,
It was my quetion as whether it will degrade the performance or not?
Thanks,
JJ
"bert" <bertcord@.gmail.com> wrote in message
news:1107297013.482698.267950@.l41g2000cwc.googlegroups.com...
> Recycle more often then. How did you determine that it "degraded"
> performance?
> bert
>|||Hi
Not that I have ever found. Output to the log file is appended and is not
read by SQL Server itself.
The bigger issue is how do you view it. A 10Mb log file does take a while to
open in EM (or notepad).
We cycle our error logs on our 400 servers every night. This helps us to
keep the Error log entries by day.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"John Smith" <JJSmith45@.hotmail.com> wrote in message
news:#bkfy5KCFHA.3524@.TK2MSFTNGP15.phx.gbl...
> Sorry,
> It was my quetion as whether it will degrade the performance or not?
> Thanks,
> JJ
> "bert" <bertcord@.gmail.com> wrote in message
> news:1107297013.482698.267950@.l41g2000cwc.googlegroups.com...
>|||"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:euXu08KCFHA.1936@.TK2MSFTNGP14.phx.gbl...
> Hi
> Not that I have ever found. Output to the log file is appended and is not
> read by SQL Server itself.
> The bigger issue is how do you view it. A 10Mb log file does take a while
to
> open in EM (or notepad).
> We cycle our error logs on our 400 servers every night. This helps us to
> keep the Error log entries by day.
>
We do it on the first of the month. But same idea.. keep it somewhat
reasonable and have enough "old" ones to troubleshoot problems.|||Another helpful hint: either by registry key or by using SQLEM, you can
modify the properties of the SQL Error logs to increase the number retained.
We set ours to 32 and recycle at 11:59 PM every night.
Another thing to consider, most of what is output to the SQL Server Error
logs also ends up in the server's Application Event log; so, you might want
to increase the size of that log too.
Finally, if you have your security settings to Audit all logins, both the
SQL Server Error logs and the system's Application Event logs can be
enourmous. We currently only set for failed login attempts.
Sincerely,
Anthony Thomas
"Greg D. Moore (Strider)" <mooregr_deleteth1s@.greenms.com> wrote in message
news:EthMd.26166$ZD1.5393@.twister.nyroc.rr.com...
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:euXu08KCFHA.1936@.TK2MSFTNGP14.phx.gbl...
> Hi
> Not that I have ever found. Output to the log file is appended and is not
> read by SQL Server itself.
> The bigger issue is how do you view it. A 10Mb log file does take a while
to
> open in EM (or notepad).
> We cycle our error logs on our 400 servers every night. This helps us to
> keep the Error log entries by day.
>
We do it on the first of the month. But same idea.. keep it somewhat
reasonable and have enough "old" ones to troubleshoot problems.

Monday, March 12, 2012

performance : load xml file vs query xml field

Does anyone have any benchmarks or general knowledge regarding the performance System.XML 2.0 and SS05 for these two scenarios:

1. XPathDocument xpathdoc = New XPathDocument(pathToXMLFile);

2. storing the contents of the xml file in SS05 ( in a col of XML datatype ) , and using SQLHelper to load it into an xpathdoc
We haven't done such measurements. For case #2, you have a make a roundtrip to the server, which will be more costly than reading from the file, although I cannot say by how much.

I think a fairer comparison is to compare the processing for case #1 with running the query on the XML data type column at the server. XML indexes on the XML column can significantly speed up queries.

Thank you,

Shankar

Performance / Design Question

Hi all,
Ok - I'm building a database around the content of an XML file I've been
supplied with - the process is straight forward enough...
The supplier has provided in the XML file far more data/information than I
actually need at this point in time, however, there's nothing to say that
"some" of this extra information might not be needed in the future...
I have therefore been adding columns like a mad man to incorporate the data
from the beginning, so if requested later on the impact on the system, and
the turn-around will be quicker.
I then wondered "wonder if this will have any side effects?"
Lets say, to make things simple I have a table with 5 columns that I do
need, I have a file with 40 items that could potentially be columns in this
table, I decide to add these now. I run my import process and populate my
table. Lets say the database size would have been 10Mb with the 5 columns,
but now, because of the types of data, and the sizes, its not 350Mb - would
this have any impact on SQL Server's performance when queries are run
against it? Obviously the sizes above are just "figures plucked from the
air" and are not actual sizes of my database, I was just trying to show a
big markup.
I would "guess" that if I wasn't using the other columns in the queries then
it shouldn't make any difference...
Any information would be appreciated - thanks in advance,
Regards
RobRob Meade wrote:
> Hi all,
> Ok - I'm building a database around the content of an XML file I've been
> supplied with - the process is straight forward enough...
> The supplier has provided in the XML file far more data/information than I
> actually need at this point in time, however, there's nothing to say that
> "some" of this extra information might not be needed in the future...
> I have therefore been adding columns like a mad man to incorporate the dat
a
> from the beginning, so if requested later on the impact on the system, and
> the turn-around will be quicker.
> I then wondered "wonder if this will have any side effects?"
> Lets say, to make things simple I have a table with 5 columns that I do
> need, I have a file with 40 items that could potentially be columns in thi
s
> table, I decide to add these now. I run my import process and populate my
> table. Lets say the database size would have been 10Mb with the 5 columns
,
> but now, because of the types of data, and the sizes, its not 350Mb - woul
d
> this have any impact on SQL Server's performance when queries are run
> against it? Obviously the sizes above are just "figures plucked from the
> air" and are not actual sizes of my database, I was just trying to show a
> big markup.
> I would "guess" that if I wasn't using the other columns in the queries th
en
> it shouldn't make any difference...
> Any information would be appreciated - thanks in advance,
> Regards
> Rob
>
Proper indexing and normalization will affect your table performance
more than the number of columns will. I hope you're not just building a
table that mimics the structure of the XML file. For instance, consider
an XML file that contains a list of customers, a billing address for
each customer, and for some customers, an optional shipping address.
Resist the temptation to build a single table that contains two sets of
address fields - one for billing, one for shipping. Instead, build a
"Customers" table that contains identifying information for the
CUSTOMER, such as customer ID, name, account number, etc.. Build an
"Addresses" table that contains information for each ADDRESS, such as an
address ID, street address, city, state, country, etc.. Build a third
table, "CustomerAddresses", that contains maybe four columns; customer
address ID, customer ID, address ID, and address type. This table
creates a 1-to-many link between a customer and its address(es). Even
the address type could be split off into an AddressTypes table,
containing an AddressType ID and a text label describing the AddressType
(billing, shipping, etc).|||"Tracy McKibben" wrote...

> Proper indexing and normalization will affect your table performance more
> than the number of columns will.
okey dokey

> I hope you're not just building a table that mimics the structure of the
> XML file.
Nope...one element "sku" has a number of attributes, these are all in the
same table, however, each sku can also have a number of "objectives",
"topics", "members" and so on...these are currently in separate tables.
I have used the SKUID to link between these tables and the sku table.
It was really more of a question about whether or not the addition (possibly
excessive - as some of it might not be used) data would have an adverse
effect.
Thanks for your reply Tracy.
Regards
Rob|||Rob Meade (ten.bewdoowsgnikNO-SPAM@.edaem.bbor) writes:
> Ok - I'm building a database around the content of an XML file I've been
> supplied with - the process is straight forward enough...
> The supplier has provided in the XML file far more data/information than I
> actually need at this point in time, however, there's nothing to say that
> "some" of this extra information might not be needed in the future...
> I have therefore been adding columns like a mad man to incorporate the
> data from the beginning, so if requested later on the impact on the
> system, and the turn-around will be quicker.
> I then wondered "wonder if this will have any side effects?"
> Lets say, to make things simple I have a table with 5 columns that I do
> need, I have a file with 40 items that could potentially be columns in
> this table, I decide to add these now. I run my import process and
> populate my table. Lets say the database size would have been 10Mb with
> the 5 columns, but now, because of the types of data, and the sizes, its
> not 350Mb - would this have any impact on SQL Server's performance when
> queries are run against it? Obviously the sizes above are just "figures
> plucked from the air" and are not actual sizes of my database, I was
> just trying to show a big markup.
The answer is, as it often does when it comes to performance: it depends.
However, here the "it depends" has a fairly straight-forward qualification.
If you have good indexing, the cost of the extra column is moderate.
The database will grow faster, and you must pay more attention to running
backup of the database and the transaction. It will also be more important
to keep fragmentation in check. But the overall cost for performance
does not have to be more than, say, 10%.
On the other hand, if you are lax about indexing, the cost for the
extra columns can be significant (assuming that they are in the same
tables as the rest). Since the rows are wider, there are fewer rows
per page, and more pages have to be read to scan tables.
Personally, I would consider the strategy of only adding the columns
you need, but add a table to save the XML documents in, so if need
occurs later, you can recover more fields from the XML document. This
is particularly attractive, if you are on SQL 2005 where you can store
the data in column of the xml data type. The performance cost for this
extra table is nil, but of course the increased database size takes
some administrative toll as discussed above.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||Rob Meade wrote:
> Nope...one element "sku" has a number of attributes, these are all in the
> same table, however, each sku can also have a number of "objectives",
> "topics", "members" and so on...these are currently in separate tables.
> I have used the SKUID to link between these tables and the sku table.
> It was really more of a question about whether or not the addition (possib
ly
> excessive - as some of it might not be used) data would have an adverse
> effect.
Sounds like you're in good shape then. Make sure you have good indexes,
including covering indexes if appropriate, and you should be fine
performance-wise.

Friday, March 9, 2012

Performance & Timeout during auto grow in SQL 2000

We had a downtime in our Stress environement during Database Automatic Data
file grow.
The database was preallocate to 20Gb with auto increment 10%.
It seems the reallocation of the 2 Gb take minutes.
We are trying to get Best Practices in SQL 2000 to see what is recommended.
- Having a Dedicated DBA to check DB space available?
- Use or Not Auto Grow? use % versus fixed size?
The idea here is to get business justification and/or use case to help us
deciding Dedicated DBA versus specific tools & technologie.Hi
Auto grow should only be a last resort. Create the DB big enough, and then
check on it daily/weekly. You can setup an alert to fire an e-mail off if the
free space gets too low. If you have the space, grow the Db to 30Gb when the
server is not too busy.
Regards
Mike
"Fabrice PIERRE" wrote:
> We had a downtime in our Stress environement during Database Automatic Data
> file grow.
> The database was preallocate to 20Gb with auto increment 10%.
> It seems the reallocation of the 2 Gb take minutes.
> We are trying to get Best Practices in SQL 2000 to see what is recommended.
> - Having a Dedicated DBA to check DB space available?
> - Use or Not Auto Grow? use % versus fixed size?
> The idea here is to get business justification and/or use case to help us
> deciding Dedicated DBA versus specific tools & technologie.|||Hi ,Mike
I'd go with creating a database big enough with auto-grow feature.
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:ACB025A7-3ACE-4E3D-9FD2-6695A1C3AAB1@.microsoft.com...
> Hi
> Auto grow should only be a last resort. Create the DB big enough, and then
> check on it daily/weekly. You can setup an alert to fire an e-mail off if
the
> free space gets too low. If you have the space, grow the Db to 30Gb when
the
> server is not too busy.
> Regards
> Mike
> "Fabrice PIERRE" wrote:
> > We had a downtime in our Stress environement during Database Automatic
Data
> > file grow.
> > The database was preallocate to 20Gb with auto increment 10%.
> > It seems the reallocation of the 2 Gb take minutes.
> > We are trying to get Best Practices in SQL 2000 to see what is
recommended.
> > - Having a Dedicated DBA to check DB space available?
> > - Use or Not Auto Grow? use % versus fixed size?
> >
> > The idea here is to get business justification and/or use case to help
us
> > deciding Dedicated DBA versus specific tools & technologie.