August 6, 2003 at 10:44 am
I have a general question in developing against SQL Server 2000 using a MS Access 2000 "Access Data Project" (ADP):
Since the ADP uses native OLEDB to communicate with the server, I have questions concerning the following:
What is the "Distributed Transaction Coordinator" in my SQL Service Manager on the Server?
I do not find any references to "Transaction Server" so did MSDTC replace the "Transaction Server" (MTS)?
Do Access ADP's benefit from either the MSDTC or MTS?
For reference:
My Sql Server 2000 box us running on Windows 2000 server (SP3) with alot of power and memory.
August 6, 2003 at 11:34 am
Read BOL by looking for key word "MS DTC" and you will find out what is "Distributed Transaction Coordinator" and hwo/when to use it.
August 7, 2003 at 6:53 am
I believe the MS DTC is use when you want to run a distributed query/view among multiple SQL Servers. However MTS is used when you developing a 3-tier application, in this case the middle tier (COM) will reside and use MTS. check for more info on SQL BOL.
August 7, 2003 at 9:22 am
BOL does cover The "Distributed Transaction Server" pretty well, but I find very little about the MTS in there.
I do find references all over the web to it's inclusion in the "NT4 Option Pack". OK, so it was an add-on to NT4...what about it's relationship to Windows 2000 server?
Was it included, excluded, replaced...what?
August 7, 2003 at 9:25 am
It is replaced by COM+ applications in Windosw 2000.
August 7, 2003 at 9:52 am
OK, now we're getting somewhere. I'm going to stop chasing history (and my tail) now and just ask straight out.
Here's what I'm doing:
I just upgraded our company's financial services package to one that runs on Sql 2000 (hence the big machine and all that power).
We have a whole bunch of MS Access applications built to manage different aspects of daily operations. Our own "homegrown" ERP + ERM system. I want to leverage the power of this new Sql 2000 machine and get all these apps upgraded.
The Phase 1 upgrade will be MS Access ADPs because it seems to be the shortest distance between where we are and where we want to be...that is using SQL Server power+data.
The second phase may very well be an entire set of Web Apps and/or VB.Net client apps using the .Net collection of tools.
(I wish I had the time to go straight to phase 2, but I don't want the rest of the company to choke on Jet and all these MDB's while I'm getting up to speed.)
My reason for pursuing this line of questioning (MTS, MSDTC, etc) is to make sure that I know and can plan for a destination that will help us make the most of the available speed, power and flexibility.
At this stage of the game, I am coding (phase 1) and planning phase 2 (or at least trying to plan) on where I want to be by the end of the 3rd quarter of this year. I’m also trying to investigate anything that might make our phase 1 implementation better.
August 12, 2003 at 4:10 am
you say: The Phase 1 upgrade will be MS Access ADPs ..
so why you use ADP not MDB ... MDB is more powerful with SQL Server and support many features that is not found on ADP ...
I already transref my company DB from Access to SQl Server .. and I use MDB ..
please think again ..
hope this help u .. and if you need any help I am here.
Alamir Mohamed
Alamir Mohamed
Alamir_mohamed@yahoo.com
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply