Has anybody tried running a conflict search from a windows terminal server running windows server 2003 (32-bit) and doing that same EXACT search on a terminal server running windows server 2008 r2 (64-bit).
Today we timed the conflict searches on server 2003, and that search took approx 1-2 mins based on the size of our database. Doing that same search on server 2008 today resulted in a 5-6 minute search.
Not that big of deal until you start running into large conflict searches. Has anybody else experienced this and is there a resolution for this?
TM is setup identically on both servers.
Bradley & Riley PC
2007 1st Ave
Cedar Rapids IA, 52405
Information Systems Manager/Network Administrator
There are other variables that enter into speed of a conflict search. I would start by looking at the size of the index files. They are located in the lndata folder under index. If the data sizes are the same between the 2 systems, there are other things to look at. Having said all of this, Time Matters and the indexer are not 64-bit applications.
Matt Stone, LLB Premier CIC - Forum Administrator 7SecondSystem.comThe 7 Second Blog
LexisNexis Platinum Achievement Circle 2009 Top Sales Producer – Time Matters
I am not seeing the indata folder on the old terminal servers (or the new ones). Both are using a UNC path back to the database. Also TimeMatters own website says that 64-bit OS are supported.
Please see the following URL:
Sure.. supported but they are not 64 Bit applications.
The indexes are in the files folder, under index/lndata. The Time Matters database is stored in SQL. The files folder contains the other data needed by Time Matters. There is no server component of the Time Matters application.The speed of the search is affected by the network connection, the size of the data (index files) and whether the index files are being used or updated. You have to ensure the new server connects as quickly as the old server. You have to test when the indexes are not being updated, which means you have to find where the indexer is running.
The Time Matters client will search through the index files. In my experience Time Matters seems to bring the indexes to the local machine or at least there is heavy network traffic while a search is being performed. I have also seen installs where the time to search increases exponentially over time.