Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM General » View Thread |
Messages 1 to 2 of 2 total |
.lck file wierdness |
Tue, Dec 12 2006 1:34 PM | Permanent Link |
Robert Eastlack | We have a client who is getting serious slowdown when running our application and making edits to the tables. The problem occurs whether
they connect using the client/server engine or as a fileserver. This problem has been seen on two different physical servers, one running Server 2000, the other Server 2003 (both are enterprise editions). The strange thing is that when we tried using a copy of their database on our site, we had the same problem at first, but after deleting their copy of the dbisam.lck file (which was copied along with their data) the slowdown disappeared. Having them do the same thing on their server does not make a difference, however. Are there any known issues with how various versions of Windows create and/or edit this file? What could possibly cause this to happen? |
Wed, Dec 13 2006 1:35 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Robert,
<< We have a client who is getting serious slowdown when running our application and making edits to the tables. The problem occurs whether they connect using the client/server engine or as a fileserver. This problem has been seen on two different physical servers, one running Server 2000, the other Server 2003 (both are enterprise editions). The strange thing is that when we tried using a copy of their database on our site, we had the same problem at first, but after deleting their copy of the dbisam.lck file (which was copied along with their data) the slowdown disappeared. Having them do the same thing on their server does not make a difference, however. Are there any known issues with how various versions of Windows create and/or edit this file? What could possibly cause this to happen? >> Not that I'm aware of. The .lck is normally very small and is only read/edited in very specific circumstances during table creations or database opens. The rest of the time it is used for locking calls only. -- Tim Young Elevate Software www.elevatesoft.com |
This web page was last updated on Tuesday, April 23, 2024 at 08:10 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |