slxdeveloper.com Community Forums

The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!

Administration Forums - Installation
Forum to discuss installing SalesLogix and general installation topics. View the code of conduct for posting guidelines.

Forums RSS Feed

Back to Forum List | Back to Installation | New Thread

View: Search:

Author

Thread: TempDB/SyncLogs Same Drive

Yup.
Posts: 126

TempDB/SyncLogs Same Drive Your last visit to this thread was on 1/1/1970 12:00:00 AM

Posted: 24 Mar 08 3:43 PM

I have noticed that the tempdb is on the same physical drive as the SyncLogs directory. Could this configuration cause any type of a performance hit? My thinking being if the tempdb is locked up and someone attaches a document, there could be a hit on I/O. Also, given all other databases on this instance are on the same physical drive, why would the tempdb have been placed on a separate drive. Note that physical drive space is not an issue.

[Reply][Quote]

Mike Spragg
Posts: 1226

Re: TempDB/SyncLogs Same Drive Your last visit to this thread was on 1/1/1970 12:00:00 AM

Posted: 25 Mar 08 9:29 AM

Locking is handled by SQL Server - not the O/S so you wouldn't get a conflict on a lock. I/O wouldn't be an issue in this case as SQL will be waiting on a lock - but there'd be enough free space is the Q to pass in the file without issue. Placing it on a different drive is a good idea for other reasons (sorting etc.) and the rule of thumb is always "more drives, more adapters = more I/O".

[Reply][Quote]

Page 1 of 1

You can subscribe to receive a daily forum digest in your user profile. View the site code of conduct for posting guidelines.

Forum RSS Feed - Subscribe to the forum RSS feed to keep on top of the latest forum activity!

slxdeveloper.com is brought to you courtesy of Ryan Farley & Customer FX Corporation. This site, and all contents herein, are Copyright © 2024 Customer FX Corporation. The information and opinions expressed here are not endorsed by Sage Software.	code of conduct \|

page cache (param): 11/26/2024 11:47:54 AM