We have a large application developed in Delphi 2007. We use SDAC components heavily to connect to MS SQL Server in a 2-Tier Client-Server environment.
Now, we want to change our apps to a 3-Tier Architecture access to avoid exposing SQL Server to the Internet ( so it is only exposed to the middle-tier access behind the firewall ). The question is, is there an easy way to convert these to 3-Tier approach, where TMSConnection on the client app can point to some proxy remote Server in the middle-tier and all the DB requests are transacted through the middle-tier with the MSSQL Server?
Any existing solution that requires bare minimum of changes for the SDAC components?
Can you suggest any other approaches/ frameworks?
I know some out there like RemObjects Data Abstract or Delphi DataSnap or TMS Software, but these need complete restructuring of the apps.
Search found 6 matches
- Thu 14 Apr 2022 15:27
- Forum: SQL Server Data Access Components
- Topic: Middle-Tier access
- Replies: 0
- Views: 15280
- Thu 09 May 2019 19:21
- Forum: SQL Server Data Access Components
- Topic: TMSQuery with FetchAll=False
- Replies: 1
- Views: 4836
TMSQuery with FetchAll=False
Hi,
We are using SDAC Version 6.11.23 for RAD Studio 2007.
We are having an issue with TMSQuery Component used with FetchAll=False (FetchRows=100). This keeps the SQL query in the SQL Server in 'pending' state (releases only after the dbgrid has fetched all records). This 'pending' state locks all other SQL processes that require an exclusive use of the same table, ultimately causing a deadlock state. What can be done so the query when used with FETCHALL=FALSE does not keep itself in pending state in the SQL Server?
Thanks
We are using SDAC Version 6.11.23 for RAD Studio 2007.
We are having an issue with TMSQuery Component used with FetchAll=False (FetchRows=100). This keeps the SQL query in the SQL Server in 'pending' state (releases only after the dbgrid has fetched all records). This 'pending' state locks all other SQL processes that require an exclusive use of the same table, ultimately causing a deadlock state. What can be done so the query when used with FETCHALL=FALSE does not keep itself in pending state in the SQL Server?
Thanks
- Wed 14 May 2014 17:23
- Forum: SQL Server Data Access Components
- Topic: SDAC Ver. 6.10.19 for XE6
- Replies: 1
- Views: 1344
SDAC Ver. 6.10.19 for XE6
I installed SDAC Ver. 6.10.19 for XE6. When restarting XE6, it throws access violation for 'DataSetManager'.
To fix this, I had to rename the registry key 'HKEY_CURRENT_USER\Software\Devart\DataSetManager\BDS\13.0' to '14.0'.
To fix this, I had to rename the registry key 'HKEY_CURRENT_USER\Software\Devart\DataSetManager\BDS\13.0' to '14.0'.
- Wed 08 Feb 2012 22:12
- Forum: SQL Server Data Access Components
- Topic: QueryRecCount and Distinct
- Replies: 5
- Views: 1269
- Wed 01 Feb 2012 17:14
- Forum: SQL Server Data Access Components
- Topic: QueryRecCount and Distinct
- Replies: 5
- Views: 1269
QueryRecCount and Union
QueryRecCount also throws error when there is 'UNION' in the sql statement.
- Mon 30 Jan 2012 22:05
- Forum: SQL Server Data Access Components
- Topic: QueryRecCount and Distinct
- Replies: 5
- Views: 1269
QueryRecCount and Distinct
I am using Delphi 2007 and SDAC Professional Version 6.0.2. TMSQuery with FetchAll=False and QueryRecCount=True is giving incorrect recordcount when there is 'Distinct' in the sql statement for the query. It doesn't seem to take 'Distinct' in account for recordcount. What is the solution?