JWColby
jwcolby at colbyconsulting.com
Thu Aug 31 08:26:16 CDT 2006
Thanks Stuart, that is what I suspected. I am trying to get a handle on how to distribute work on the machines, i.e. actual machine cycles. John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Stuart McLachlan Sent: Thursday, August 31, 2006 8:34 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Which machine does the work? On 31 Aug 2006 at 7:54, JWColby wrote: > I have two machines, both running SQL Server instances. MachineA has > registered the database on MachineA and the database on MachineB. MachineB > has done likewise. I think you mean you have registered the *Server* on MachineB in EM on MachineA and vice versa. You don't register databases, you register servers. > MachineA holds a database with a table to which I want to add an > index. If I open EM on MachineB, select the database on MachineA, > open a table in design view and "add an index", where is the work performed? > Does MachineB actually do anything? No, >Or does MachineB simply send a command > to the SQL Server instance on MachineA telling it to add the index and >all of the work is performed on MachineA? Yes. Whatever server has the database attached to it does all the work on that database. That's the whole point of a client/server application. Think what happens if you install EM on a MachineC with no SQL Server instance running on it. When you register the instances on MachineA and MachineB, you can do anything you like with them, but there is no MachineC instance to do any of the work - it has to be done by the instance which actually hosts the database. -- Stuart _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com