Shamil Salakhetdinov
shamil at users.mns.ru
Tue May 8 17:25:40 CDT 2007
Hi Arthur, Using MS SQL on middle-/business tier as a separate physical server instance could be needed for the "heavy" business tasks: e.g. (reporting) stored procedures using large temp tables, cursors, XML etc. (Partially) separating business tier lets to keep data tier working effectively in this case. Middle tier "Miss Middleton" is an abstraction layer. I didn't say in this thread that this "Miss Middleton" should be completely moved to a separate MS SQL Server instance nor did I say developers should program directly against database tables.... -- Shamil -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Arthur Fuller Sent: Tuesday, May 08, 2007 6:17 PM To: Access Developers discussion and problem solving Subject: Re: [AccessD] Lazy,or Agile: that is the question... - Was Re:When to UseaJunctionTable There is no requirement for the middle tier to have a new instance of SQL. In fact I have no idea how you arrived at that thought. The general thinking behind 3-tier architecture is this: 1. client has minimal hardware and minimal installation. Client software has no idea where the database lives, and speaks only to Miss Middleton. 2. Miss Middleton treats all her clients as equally worthless, but does translate their requests into requests from the database, whose address only Miss Middleton knows. 3. The database developers are free to rewite any sprocs and UDFs and views as they please, so long as Miss Middleton is undisturbed. They can even redesign tables, since any good designer forbids direct access to tables. So middle-tier Miss Middleton controls every access to every table, whether it be through a sproc or udf or view or materialized view. Arthur On 5/8/07, Gustav Brock <Gustav at cactus.dk> wrote: > > Hi Shamil > > I must believe you here as I haven't done much programming in SQL Server > and you have so much more experience in this area. > However, to me a middle-tier can be made from anything that fits the > purpose, and if that calls for another instance of SQL Server, that's fine > with me. Actually, it sounds like it could be a very clever solution. > > /gustav > > -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com