I'm looking at a multiuser CRM or ERP style application with a Windows client and a central SQL Server, but no separate application server or web component. Was this a common design?
Was it common for desktop apps to connect straight to SQL Server?
Answers
Yes. That's usually called a two-tier client-server application. The desktop program connects directly to the database, rather than sending requests through a separate application server. It was common before browser-based business software became widespread, and systems built this way are still around.
That doesn't mean every older application worked this way. Some had application servers, and others used terminals connected to a central system.
Reply to this answer
The absence of an application server doesn't necessarily mean all the business logic runs on the desktop. Some systems put a lot of it in database stored procedures, while the client mainly handles the interface and calls those procedures.
If you're supporting one, check both the client and the database before deciding where a calculation or validation happens. There may be a substantial amount of application behavior on the SQL Server itself.
Reply to this answer
From a support angle, the clients can be the awkward part. You may need database drivers and connection settings on each PC, and a software change can mean updating every installation. Some organizations used terminal servers to centralize the desktop application instead.
Reply to this answer
Local processing also made sense when desktop resources were relatively cheap and network connections were limited. Some applications even supported work away from a reliable connection and loaded batches of data later. That's a particular design, though, not something to assume just because a client connects directly to SQL.
Reply to this answer
Add your answer
Answers are reviewed before publication.
3s!lilacwrench_694:
So two-tier describes the connection layout, not necessarily which machine does most of the processing.