Re: Full Text File Locations - Best Practices
- From: "Arnie Rowland" <arnie@xxxxxxxx>
- Date: Tue, 15 Aug 2006 23:09:35 -0700
Any time you have enough LUNs or Drives, then every file should have its own
I/O thread.
Otherwise, evaluate the 'traffic' for the file. With a large amount of
read/write activity, a separate drive/LUN would be helpful. With lesser
amounts of traffic, trade-offs become necessary.
Generally accepted 'Best Practice':
Logs on dedicated drive/LUN.
Database on dedicated drive/LUN
TempDb on dedicated drive/LUN
With limited options, whether to put the F/T catalog files on the same
drive/LUN as the database or the TempDb would depend upon the application
design and traffic. A well behaved OLTP application, using tightly
controlled small queries, may not have much demand on the TempDb drive/LUN.
I would run some metrics on the Database and TempDb drives/LUNs to determine
which has the most 'slack'.
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"tduffy77 via SQLMonster.com" <u24228@uwe> wrote in message
news:649fb58d447d3@xxxxxx
Any suggestions and/or supporting documentation for best practices on
where
to locate the full text catalog files. Especially as related to other
data,
log, and tempdb files?
My searching is coming up empty.
Thanks in advance.
Terry
--
Message posted via http://www.sqlmonster.com
.
- References:
- Full Text File Locations - Best Practices
- From: tduffy77 via SQLMonster.com
- Full Text File Locations - Best Practices
- Prev by Date: Full Text File Locations - Best Practices
- Next by Date: Re: SELECT DISTINCT records based only on two columns
- Previous by thread: Full Text File Locations - Best Practices
- Next by thread: Re: SELECT DISTINCT records based only on two columns
- Index(es):
Relevant Pages
|
|
