Bug? Column Default Disappears when Reinitializing Replication

Hi Gurus,
I have a default on a column that disappears every time I reinitialize
replication. This is transactional replication to an updatable subscriber on
SQL Server 2005. Yes, replication of defaults is turned on, and *most* of my
column defaults do, in fact, replicate to the subscriber. The ones that fail
are distinctive in that they reference a user-defined function. And yes,
that UDF and all its internal dependencies are present on the subscriber.
(All the defaults that successfully replicate are either literal values or
else reference *intrinsic* functions, e.g. GETDATE.)
Any idea whether this is a bug? Or what? Any help would be *VERY*
appreciated!
Thanks!
Jason Fisher
Did you replicate the UDFs referenced by the defaults as well, would be
great if you can post the history of the snapshot agent as well. Thanks
much.
-Raymond
"Jason Fisher" <j.fisher@.earthlink.net> wrote in message
news:uaU5n8waHHA.4396@.TK2MSFTNGP06.phx.gbl...
> Hi Gurus,
> I have a default on a column that disappears every time I reinitialize
> replication. This is transactional replication to an updatable subscriber
> on SQL Server 2005. Yes, replication of defaults is turned on, and *most*
> of my column defaults do, in fact, replicate to the subscriber. The ones
> that fail are distinctive in that they reference a user-defined function.
> And yes, that UDF and all its internal dependencies are present on the
> subscriber. (All the defaults that successfully replicate are either
> literal values or else reference *intrinsic* functions, e.g. GETDATE.)
> Any idea whether this is a bug? Or what? Any help would be *VERY*
> appreciated!
> Thanks!
> Jason Fisher
>
|||Raymond,
Thanks for the reply. The UDF is not being *replicated* -- currently, we
aren't replicating any of the code objects (e.g., stored procedures,
functions, or triggers) -- but it was copied to the subscriber database
manually (ahead of time). It did exist there at the time replication was
initialized. But does it have to be explicitly *included* in the replication
articles? I wouldn't have thought so.
Jason
"Raymond Mak [MSFT]" <rmak@.online.microsoft.com> wrote in message
news:ew9MKFxaHHA.1400@.TK2MSFTNGP06.phx.gbl...[vbcol=seagreen]
> Did you replicate the UDFs referenced by the defaults as well, would be
> great if you can post the history of the snapshot agent as well. Thanks
> much.
> -Raymond
> "Jason Fisher" <j.fisher@.earthlink.net> wrote in message
> news:uaU5n8waHHA.4396@.TK2MSFTNGP06.phx.gbl...
|||The problem is that we can't just assume that you have the UDFs referenced
by the defaults\check constraints to be at the subscriber ahead of time so
you have two options:
1) Explicitly include the UDFs referenced by the defaults in your
publication
2) Put the defaults referencing the unpublished UDFs in a post-snapshot
script, this basically means you know better than we do what you have at
your subscriber (After all, you did manually create the UDFs at the
subscriber right?)
-Raymond
"Jason Fisher" <j.fisher@.earthlink.net> wrote in message
news:OsG3BaxaHHA.4948@.TK2MSFTNGP05.phx.gbl...
> Raymond,
> Thanks for the reply. The UDF is not being *replicated* -- currently, we
> aren't replicating any of the code objects (e.g., stored procedures,
> functions, or triggers) -- but it was copied to the subscriber database
> manually (ahead of time). It did exist there at the time replication was
> initialized. But does it have to be explicitly *included* in the
> replication articles? I wouldn't have thought so.
> Jason
> "Raymond Mak [MSFT]" <rmak@.online.microsoft.com> wrote in message
> news:ew9MKFxaHHA.1400@.TK2MSFTNGP06.phx.gbl...
>
|||Raymond,

> The problem is that we can't just assume that you have the UDFs referenced
> by the defaults\check constraints to be at the subscriber ahead of time so
> you have two options:
Hmm. But wouldn't it make more sense to replicate the default and then throw
an error later if the referenced UDF is not there on the subscriber, rather
than to simply fail silently during replication? I would always rather have
a noisy, trappable error later on than a silent, untrappable "error" earlier
on. Oh well ...
Regarding your recommendations:

> 1) Explicitly include the UDFs referenced by the defaults in your
> publication
I'm trying this now, but it doesn't look like a good solution in our
particular case because we have tables already in the subscriber database
(not being replicated from the publisher) that also reference the same UDF.
This means that what I'm seeing is error after error in the replication
monitor as it tries and fails to drop the UDF.

> 2) Put the defaults referencing the unpublished UDFs in a post-snapshot
> script, this basically means you know better than we do what you have at
> your subscriber (After all, you did manually create the UDFs at the
> subscriber right?)
I will think about trying this next, although it's not ideal because a) it's
manual, b) the tables in the script have to be updated / maintained as / if
our business needs change. In other words: again, it's manual.
Any other ideas? And thanks very much for the assistance, too, by the way!

Jason
|||> Hmm. But wouldn't it make more sense to replicate the default and then
> throw an error later if the referenced UDF is not there on the subscriber,
> rather than to simply fail silently during replication? I would always
> rather have a noisy, trappable error later on than a silent, untrappable
> "error" earlier on. Oh well ...
I believe the snapshot agent did print out messages explaining that a
default\check constraint is not scripted because it references udf not in
the publication; and believe me when I say some folks will complain the
other way if the snapshot fails to apply because we "should know better" not
to script a default constraint that is referencing something that they
"explicitly" exclude from the publication. The perfect solution will be for
us to divine what the user really wants but we are not there yet and will
not likely be there in the near future.
-Raymond
"Jason Fisher" <j.fisher@.earthlink.net> wrote in message
news:uobv$TyaHHA.4716@.TK2MSFTNGP02.phx.gbl...
> Raymond,
>
> Hmm. But wouldn't it make more sense to replicate the default and then
> throw an error later if the referenced UDF is not there on the subscriber,
> rather than to simply fail silently during replication? I would always
> rather have a noisy, trappable error later on than a silent, untrappable
> "error" earlier on. Oh well ...
> Regarding your recommendations:
>
> I'm trying this now, but it doesn't look like a good solution in our
> particular case because we have tables already in the subscriber database
> (not being replicated from the publisher) that also reference the same
> UDF. This means that what I'm seeing is error after error in the
> replication monitor as it tries and fails to drop the UDF.
>
> I will think about trying this next, although it's not ideal because a)
> it's manual, b) the tables in the script have to be updated / maintained
> as / if our business needs change. In other words: again, it's manual.
> Any other ideas? And thanks very much for the assistance, too, by the way!
>
> Jason
>
|||Now that I have thought about your case some more, you can publish the UDFs
referenced by the default constraint while making sure that the pre-creation
command for the UDF articles is 'none' instead of 'drop'. This will avoid
having the snapshot delivery process from trying to drop the UDFs at your
subscriber which is most likely the main source of problem for replicating
the UDFs to the subscriber.
-Raymond
"Jason Fisher" <j.fisher@.earthlink.net> wrote in message
news:uobv$TyaHHA.4716@.TK2MSFTNGP02.phx.gbl...
> Raymond,
>
> Hmm. But wouldn't it make more sense to replicate the default and then
> throw an error later if the referenced UDF is not there on the subscriber,
> rather than to simply fail silently during replication? I would always
> rather have a noisy, trappable error later on than a silent, untrappable
> "error" earlier on. Oh well ...
> Regarding your recommendations:
>
> I'm trying this now, but it doesn't look like a good solution in our
> particular case because we have tables already in the subscriber database
> (not being replicated from the publisher) that also reference the same
> UDF. This means that what I'm seeing is error after error in the
> replication monitor as it tries and fails to drop the UDF.
>
> I will think about trying this next, although it's not ideal because a)
> it's manual, b) the tables in the script have to be updated / maintained
> as / if our business needs change. In other words: again, it's manual.
> Any other ideas? And thanks very much for the assistance, too, by the way!
>
> Jason
>

Bug in SQL Server 2005 CE ?

Hello,

I have some trouble with using Merge replication with SQL CE 3.0 (SQL Server 2005 CE).

I've develop a framework that make transition between SQL CE and Business Object (generic framework that use XML for mapping).

My trouble is that I can't upgrade SQL and so use merge replication or the reverse (replication and so upgrade)
When I did this, Visual Studio shows me that I lost connection with the PDA, and on the PDA, I see the error reporting that ask me if I want to send it to Microsoft... (the report contains only number of version and lot of hexadecimal code)
I have no Exception on Visual Studio that I can use for debug this trouble...

Whereas, when I launch this application, I did a merge replication, and stop the program. I relaunch it and make Upgrade And it's work.... (the reverse too)

I check in my code if I forgot to close connection on SQL Ce or else but I didn't find anything...

Anyone have already see this bug ? Or/And have you a pist for resolve it ?

For information:
I use :
SQL Server 2005 Compact Edition (Sql Ce 3.0)
SQL Server 2005 Standard or Entreprise SP1 on Windows Server 2003 (on Virtual Machine)
Compact Framework 2
Windows Mobile 5 and 6 on Emulator
To see if the trouble is cause by my framework, I try to take out the use of my framework and put a easy code.

But the result is the same... I can't make an update + replication.

Here my code :

First, this occur when I press the first button (update) :

Cursor.Current = Cursors.WaitCursor;
SqlCeConnection _conn = new SqlCeConnection(connexionstring);
_conn.Open();
SqlCeCommand _comm = _conn.CreateCommand();
string _req = "UPDATE Employee SET LastName = 'Damien' WHERE EmployeeID = '1'";
_comm.CommandText = _req;
_comm.CommandType = CommandType.Text;
_comm.ExecuteNonQuery();
_comm.Dispose();
_conn.Close();
_conn.Dispose();
Cursor.Current = Cursors.Default;

And now, the second button (Replicate) :

Cursor.Current = Cursors.WaitCursor;
SqlCeReplication repl = new SqlCeReplication();
repl.InternetUrl = @."http://192.168.0.1/Publication/sqlcesa30.dll";
repl.Publisher = @."w2003Mobile";
repl.PublisherDatabase = @."Prototype";
repl.PublisherSecurityMode = SecurityType.NTAuthentication;
repl.Publication = @."PubliProto";
repl.Subscriber = @."Subscription";
repl.SubscriberConnectionString = connexionstring;
try
{
repl.Synchronize(); //Bien dans un Try/Catch mais je n'obtiens pas d'exception..... juste le rapport d'erreur
}
catch (Exception ex)
{
throw new Exception("Erreur lors de la synchronisation", ex);
}
repl.Dispose();
Cursor.Current = Cursors.Default;

As when I test my framework, this code works when I try it separately (with shutdown of my application between two).
But when I try to Update and next Replicate, or reverse, it show me an error report...

I don't know why I've this probleme, so if someone can help me
|||Nobody have some idea ?

I post 2 pictures that shows the error report :

Note the value of the API Cur Process is strange, isn't it ?

BUG IN MANAGEMENT STUDIO

I get this blow up and can reproduce it at will.
I am not going to pay to report a bug.
I also have another problem with replication. The wizard fails with a
message saying" invalid column name "options"", but I don't gave any column
named options in any table or view.
philip_38@.hotmail.com.
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.ArgumentOutOfRangeException: InvalidArgument=Value of '52' is not
valid for 'index'.
Parameter name: index
at System.Windows.Forms.ListView.ListViewItemCollecti on.get_Item(Int32
index)
at System.Windows.Forms.ListView.set_VirtualListSize( Int32 value)
at
Microsoft.SqlServer.Management.UI.VSIntegration.Ap pIDPackage.RightPaneListViewer.set_VirtualListSize (Int32 value)
at
Microsoft.SqlServer.Management.UI.VSIntegration.Ap pIDPackage.RightPaneListViewer.RemoveItems(IList`1 items)
at
Microsoft.SqlServer.Management.UI.VSIntegration.Ap pIDPackage.RightPaneControl.RemoveItemsFromReport( INodeInformation[] nodes)
at
Microsoft.SqlServer.Management.UI.VSIntegration.Ap pIDPackage.RightPaneToolWindow.OnNodesRemoved(Obje ct sender, NodesChangedEventArgs args)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
AppIDPackage
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/AppIDPackage.DLL
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
Microsoft.SqlServer.SqlTools.VSIntegration
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.SqlTools.VSIntegration.DLL
Microsoft.VisualStudio.Shell.Interop
Assembly Version: 7.1.40304.0
Win32 Version: 7.0.4054
CodeBase:
file:///C:/WINDOWS/assembly/GAC/Microsoft.VisualStudio.Shell.Interop/7.1.40304.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.Shell.Interop.dll
Microsoft.VisualStudio.OLE.Interop
Assembly Version: 7.1.40304.0
Win32 Version: 7.0.4054
CodeBase:
file:///C:/WINDOWS/assembly/GAC/Microsoft.VisualStudio.OLE.Interop/7.1.40304.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.OLE.Interop.dll
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
Microsoft.SqlServer.SqlTDiagM
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.SqlTDiagM/9.0.242.0__89845dcd8080cc91/Microsoft.SqlServer.SqlTDiagM.dll
Microsoft.DataWarehouse.SQM
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.DataWarehouse.SQM.DLL
Microsoft.SqlServer.Instapi
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.Instapi/9.0.242.0__89845dcd8080cc91/Microsoft.SqlServer.Instapi.dll
ObjectExplorer
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/ObjectExplorer.DLL
ConnectionDlg
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/ConnectionDlg.DLL
Microsoft.SqlServer.CustomControls
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.CustomControls/9.0.242.0__89845dcd8080cc91/Microsoft.SqlServer.CustomControls.dll
SqlWorkbench.Interfaces
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/SqlWorkbench.Interfaces.DLL
Accessibility
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
Microsoft.SqlServer.RegSvrEnum
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.RegSvrEnum/9.0.242.0__89845dcd8080cc91/Microsoft.SqlServer.RegSvrEnum.dll
SqlMgmt
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/SqlMgmt.DLL
EnvDTE
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC/EnvDTE/8.0.0.0__b03f5f7f11d50a3a/EnvDTE.dll
Microsoft.NetEnterpriseServers.ExceptionMessageBox
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.NetEnterpriseServers.ExceptionMessageBox /9.0.242.0__89845dcd8080cc91/Microsoft.NetEnterpriseServers.ExceptionMessageBox .dll
System.Data
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_32/System.Data/2.0.0.0__b77a5c561934e089/System.Data.dll
Microsoft.SqlServer.ConnectionInfo
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.ConnectionInfo/9.0.242.0__89845dcd8080cc91/Microsoft.SqlServer.ConnectionInfo.dll
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
Microsoft.SqlServer.SmoEnum
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.SmoEnum/9.0.242.0__89845dcd8080cc91/Microsoft.SqlServer.SmoEnum.dll
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
System.Transactions
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_32/System.Transactions/2.0.0.0__b77a5c561934e089/System.Transactions.dll
System.EnterpriseServices
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_32/System.EnterpriseServices/2.0.0.0__b03f5f7f11d50a3a/System.EnterpriseServices.dll
Microsoft.SqlServer.Smo
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.Smo/9.0.242.0__89845dcd8080cc91/Microsoft.SqlServer.Smo.dll
Microsoft.SqlServer.SqlEnum
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.SqlEnum/9.0.242.0__89845dcd8080cc91/Microsoft.SqlServer.SqlEnum.dll
Microsoft.SqlServer.BatchParser
Assembly Version: 9.0.242.0
Win32 Version: 2005.090.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_32/Microsoft.SqlServer.BatchParser/9.0.242.0__89845dcd8080cc91/Microsoft.SqlServer.BatchParser.dll
msvcm80
Assembly Version: 8.0.50608.0
Win32 Version: 8.00.50727.42
CodeBase:
file:///C:/WINDOWS/WinSxS/x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727. 42_x-ww_0DE06ACD/msvcm80.dll
ObjectExplorerReplication
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/ObjectExplorerReplication.DLL
Microsoft.ReportViewer.WinForms
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.42
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.ReportViewer.WinForms/8.0.0.0__b03f5f7f11d50a3a/Microsoft.ReportViewer.WinForms.dll
System.Management
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/System.Management/2.0.0.0__b03f5f7f11d50a3a/System.Management.dll
SQLEditors
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/SQLEditors.DLL
Microsoft.VisualStudio.TextManager.Interop
Assembly Version: 7.1.40304.0
Win32 Version: 7.0.4054
CodeBase:
file:///C:/WINDOWS/assembly/GAC/Microsoft.VisualStudio.TextManager.Interop/7.1.40304.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.TextManager.Interop.dll
Microsoft.SqlServer.GridControl
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.GridControl/9.0.242.0__89845dcd8080cc91/Microsoft.SqlServer.GridControl.dll
Microsoft.SqlServerCe.Client
Assembly Version: 9.0.242.0
Win32 Version: 3.0.5207.0
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServerCe.Client.DLL
SqlManagerUI
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/SqlManagerUI.DLL
Microsoft.AnalysisServices
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.AnalysisServices/9.0.242.0__89845dcd8080cc91/Microsoft.AnalysisServices.dll
Microsoft.SqlServer.DlgGrid
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.DlgGrid/9.0.242.0__89845dcd8080cc91/Microsoft.SqlServer.DlgGrid.dll
Microsoft.SqlServer.DataStorage
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.DataStorage/9.0.242.0__89845dcd8080cc91/Microsoft.SqlServer.DataStorage.dll
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
Philip Orleans wrote:

> I get this blow up and can reproduce it at will.
> I am not going to pay to report a bug.
> I also have another problem with replication. The wizard fails with a
> message saying" invalid column name "options"", but I don't gave any column
> named options in any table or view.
> philip_38@.hotmail.com.
>
The support policy says that MS doesn't charge for bug reports (they
refund your advance charges). You can also file bugs online at the
Product Feedback Centre:
http://lab.msdn.microsoft.com/productfeedback/
David Portas
SQL Server MVP

BUG IN MANAGEMENT STUDIO

I get this blow up and can reproduce it at will.
I am not going to pay to report a bug.
I also have another problem with replication. The wizard fails with a
message saying" invalid column name "options"", but I don't gave any column
named options in any table or view.
philip_38@.hotmail.com.
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.ArgumentOutOfRangeException: InvalidArgument=Value of '52' is not
valid for 'index'.
Parameter name: index
at System.Windows.Forms.ListView.ListViewItemCollection.get_Item(Int32
index)
at System.Windows.Forms.ListView.set_VirtualListSize(Int32 value)
at
Microsoft.SqlServer.Management.UI.VSIntegration.AppIDPackage.RightPaneListViewer.set_VirtualListSize(Int32 value)
at
Microsoft.SqlServer.Management.UI.VSIntegration.AppIDPackage.RightPaneListViewer.RemoveItems(IList`1 items)
at
Microsoft.SqlServer.Management.UI.VSIntegration.AppIDPackage.RightPaneControl.RemoveItemsFromReport(INodeInformation[] nodes)
at
Microsoft.SqlServer.Management.UI.VSIntegration.AppIDPackage.RightPaneToolWindow.OnNodesRemoved(Object sender, NodesChangedEventArgs args)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
---
AppIDPackage
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/AppIDPackage.DLL
---
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
---
Microsoft.SqlServer.SqlTools.VSIntegration
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.SqlTools.VSIntegration.DLL
---
Microsoft.VisualStudio.Shell.Interop
Assembly Version: 7.1.40304.0
Win32 Version: 7.0.4054
CodeBase:
file:///C:/WINDOWS/assembly/GAC/Microsoft.VisualStudio.Shell.Interop/7.1.40304.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.Shell.Interop.dll
---
Microsoft.VisualStudio.OLE.Interop
Assembly Version: 7.1.40304.0
Win32 Version: 7.0.4054
CodeBase:
file:///C:/WINDOWS/assembly/GAC/Microsoft.VisualStudio.OLE.Interop/7.1.40304.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.OLE.Interop.dll
---
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
---
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
---
Microsoft.SqlServer.SqlTDiagM
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.SqlTDiagM/9.0.242.0__89845dcd8080cc91/Microsoft.SqlServer.SqlTDiagM.dll
---
Microsoft.DataWarehouse.SQM
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.DataWarehouse.SQM.DLL
---
Microsoft.SqlServer.Instapi
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.Instapi/9.0.242.0__89845dcd8080cc91/Microsoft.SqlServer.Instapi.dll
---
ObjectExplorer
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/ObjectExplorer.DLL
---
ConnectionDlg
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/ConnectionDlg.DLL
---
Microsoft.SqlServer.CustomControls
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.CustomControls/9.0.242.0__89845dcd8080cc91/Microsoft.SqlServer.CustomControls.dll
---
SqlWorkbench.Interfaces
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/SqlWorkbench.Interfaces.DLL
---
Accessibility
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
---
Microsoft.SqlServer.RegSvrEnum
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.RegSvrEnum/9.0.242.0__89845dcd8080cc91/Microsoft.SqlServer.RegSvrEnum.dll
---
SqlMgmt
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/SqlMgmt.DLL
---
EnvDTE
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC/EnvDTE/8.0.0.0__b03f5f7f11d50a3a/EnvDTE.dll
---
Microsoft.NetEnterpriseServers.ExceptionMessageBox
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.NetEnterpriseServers.ExceptionMessageBox/9.0.242.0__89845dcd8080cc91/Microsoft.NetEnterpriseServers.ExceptionMessageBox.dll
---
System.Data
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_32/System.Data/2.0.0.0__b77a5c561934e089/System.Data.dll
---
Microsoft.SqlServer.ConnectionInfo
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.ConnectionInfo/9.0.242.0__89845dcd8080cc91/Microsoft.SqlServer.ConnectionInfo.dll
---
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
---
Microsoft.SqlServer.SmoEnum
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.SmoEnum/9.0.242.0__89845dcd8080cc91/Microsoft.SqlServer.SmoEnum.dll
---
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
---
System.Transactions
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_32/System.Transactions/2.0.0.0__b77a5c561934e089/System.Transactions.dll
---
System.EnterpriseServices
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_32/System.EnterpriseServices/2.0.0.0__b03f5f7f11d50a3a/System.EnterpriseServices.dll
---
Microsoft.SqlServer.Smo
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.Smo/9.0.242.0__89845dcd8080cc91/Microsoft.SqlServer.Smo.dll
---
Microsoft.SqlServer.SqlEnum
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.SqlEnum/9.0.242.0__89845dcd8080cc91/Microsoft.SqlServer.SqlEnum.dll
---
Microsoft.SqlServer.BatchParser
Assembly Version: 9.0.242.0
Win32 Version: 2005.090.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_32/Microsoft.SqlServer.BatchParser/9.0.242.0__89845dcd8080cc91/Microsoft.SqlServer.BatchParser.dll
---
msvcm80
Assembly Version: 8.0.50608.0
Win32 Version: 8.00.50727.42
CodeBase:
file:///C:/WINDOWS/WinSxS/x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.42_x-ww_0DE06ACD/msvcm80.dll
---
ObjectExplorerReplication
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/ObjectExplorerReplication.DLL
---
Microsoft.ReportViewer.WinForms
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.42
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.ReportViewer.WinForms/8.0.0.0__b03f5f7f11d50a3a/Microsoft.ReportViewer.WinForms.dll
---
System.Management
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/System.Management/2.0.0.0__b03f5f7f11d50a3a/System.Management.dll
---
SQLEditors
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/SQLEditors.DLL
---
Microsoft.VisualStudio.TextManager.Interop
Assembly Version: 7.1.40304.0
Win32 Version: 7.0.4054
CodeBase:
file:///C:/WINDOWS/assembly/GAC/Microsoft.VisualStudio.TextManager.Interop/7.1.40304.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.TextManager.Interop.dll
---
Microsoft.SqlServer.GridControl
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.GridControl/9.0.242.0__89845dcd8080cc91/Microsoft.SqlServer.GridControl.dll
---
Microsoft.SqlServerCe.Client
Assembly Version: 9.0.242.0
Win32 Version: 3.0.5207.0
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServerCe.Client.DLL
---
SqlManagerUI
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/SqlManagerUI.DLL
---
Microsoft.AnalysisServices
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.AnalysisServices/9.0.242.0__89845dcd8080cc91/Microsoft.AnalysisServices.dll
---
Microsoft.SqlServer.DlgGrid
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.DlgGrid/9.0.242.0__89845dcd8080cc91/Microsoft.SqlServer.DlgGrid.dll
---
Microsoft.SqlServer.DataStorage
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.DataStorage/9.0.242.0__89845dcd8080cc91/Microsoft.SqlServer.DataStorage.dll
---
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.Philip Orleans wrote:
> I get this blow up and can reproduce it at will.
> I am not going to pay to report a bug.
> I also have another problem with replication. The wizard fails with a
> message saying" invalid column name "options"", but I don't gave any column
> named options in any table or view.
> philip_38@.hotmail.com.
>
The support policy says that MS doesn't charge for bug reports (they
refund your advance charges). You can also file bugs online at the
Product Feedback Centre:
http://lab.msdn.microsoft.com/productfeedback/
--
David Portas
SQL Server MVP
--

BUG IN MANAGEMENT STUDIO

I get this blow up and can reproduce it at will.
I am not going to pay to report a bug.
I also have another problem with replication. The wizard fails with a
message saying" invalid column name "options"", but I don't gave any column
named options in any table or view.
philip_38@.hotmail.com.
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.ArgumentOutOfRangeException: InvalidArgument=Value of '52' is not
valid for 'index'.
Parameter name: index
at System.Windows.Forms.ListView.ListViewItemCollection.get_Item(Int32
index)
at System.Windows.Forms.ListView.set_VirtualListSize(Int32 value)
at
Microsoft.SqlServer.Management.UI.VSIntegration.AppIDPackage.RightPaneListVi
ewer.set_VirtualListSize(Int32 value)
at
Microsoft.SqlServer.Management.UI.VSIntegration.AppIDPackage.RightPaneListVi
ewer.RemoveItems(IList`1 items)
at
Microsoft.SqlServer.Management.UI.VSIntegration.AppIDPackage.RightPaneContro
l.RemoveItemsFromReport(INodeInformation[] nodes)
at
Microsoft.SqlServer.Management.UI.VSIntegration.AppIDPackage.RightPaneToolWi
ndow.OnNodesRemoved(Object sender, NodesChangedEventArgs args)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
---
AppIDPackage
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Co
mmon7/IDE/AppIDPackage.DLL
---
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System
.dll
---
Microsoft.SqlServer.SqlTools.VSIntegration
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Co
mmon7/IDE/Microsoft.SqlServer.SqlTools.VSIntegration.DLL
---
Microsoft.VisualStudio.Shell.Interop
Assembly Version: 7.1.40304.0
Win32 Version: 7.0.4054
CodeBase:
file:///C:/WINDOWS/assembly/GAC/Microsoft.VisualStudio.Shell.Interop/7.1.403
04.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.Shell.Interop.dll
---
Microsoft.VisualStudio.OLE.Interop
Assembly Version: 7.1.40304.0
Win32 Version: 7.0.4054
CodeBase:
file:///C:/WINDOWS/assembly/GAC/Microsoft.VisualStudio.OLE.Interop/7.1.40304
.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.OLE.Interop.dll
---
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561
934e089/System.Windows.Forms.dll
---
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3
a/System.Drawing.dll
---
Microsoft.SqlServer.SqlTDiagM
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.SqlTDiagM/9.0.242.0
__89845dcd8080cc91/Microsoft.SqlServer.SqlTDiagM.dll
---
Microsoft.DataWarehouse.SQM
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Co
mmon7/IDE/Microsoft.DataWarehouse.SQM.DLL
---
Microsoft.SqlServer.Instapi
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.Instapi/9.0.242.0__
89845dcd8080cc91/Microsoft.SqlServer.Instapi.dll
---
ObjectExplorer
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Co
mmon7/IDE/ObjectExplorer.DLL
---
ConnectionDlg
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Co
mmon7/IDE/ConnectionDlg.DLL
---
Microsoft.SqlServer.CustomControls
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.CustomControls/9.0.
242.0__89845dcd8080cc91/Microsoft.SqlServer.CustomControls.dll
---
SqlWorkbench.Interfaces
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Co
mmon7/IDE/SqlWorkbench.Interfaces.DLL
---
Accessibility
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a
/Accessibility.dll
---
Microsoft.SqlServer.RegSvrEnum
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.RegSvrEnum/9.0.242.
0__89845dcd8080cc91/Microsoft.SqlServer.RegSvrEnum.dll
---
SqlMgmt
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Co
mmon7/IDE/SqlMgmt.DLL
---
EnvDTE
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC/EnvDTE/8.0.0.0__b03f5f7f11d50a3a/EnvDTE.dll
---
Microsoft.NetEnterpriseServers.ExceptionMessageBox
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.NetEnterpriseServers.Exceptio
nMessageBox/9.0.242.0__89845dcd8080cc91/Microsoft.NetEnterpriseServers.Excep
tionMessageBox.dll
---
System.Data
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_32/System.Data/2.0.0.0__b77a5c561934e089/Sys
tem.Data.dll
---
Microsoft.SqlServer.ConnectionInfo
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.ConnectionInfo/9.0.
242.0__89845dcd8080cc91/Microsoft.SqlServer.ConnectionInfo.dll
---
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/Sy
stem.Xml.dll
---
Microsoft.SqlServer.SmoEnum
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.SmoEnum/9.0.242.0__
89845dcd8080cc91/Microsoft.SqlServer.SmoEnum.dll
---
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f1
1d50a3a/System.Configuration.dll
---
System.Transactions
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_32/System.Transactions/2.0.0.0__b77a5c561934
e089/System.Transactions.dll
---
System.EnterpriseServices
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_32/System.EnterpriseServices/2.0.0.0__b03f5f
7f11d50a3a/System.EnterpriseServices.dll
---
Microsoft.SqlServer.Smo
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.Smo/9.0.242.0__8984
5dcd8080cc91/Microsoft.SqlServer.Smo.dll
---
Microsoft.SqlServer.SqlEnum
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.SqlEnum/9.0.242.0__
89845dcd8080cc91/Microsoft.SqlServer.SqlEnum.dll
---
Microsoft.SqlServer.BatchParser
Assembly Version: 9.0.242.0
Win32 Version: 2005.090.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_32/Microsoft.SqlServer.BatchParser/9.0.242.0
__89845dcd8080cc91/Microsoft.SqlServer.BatchParser.dll
---
msvcm80
Assembly Version: 8.0.50608.0
Win32 Version: 8.00.50727.42
CodeBase:
file:///C:/WINDOWS/WinSxS/x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.
42_x-ww_0DE06ACD/msvcm80.dll
---
ObjectExplorerReplication
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Co
mmon7/IDE/ObjectExplorerReplication.DLL
---
Microsoft.ReportViewer.WinForms
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.42
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.ReportViewer.WinForms/8.0.0.0
__b03f5f7f11d50a3a/Microsoft.ReportViewer.WinForms.dll
---
System.Management
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/System.Management/2.0.0.0__b03f5f7f11d5
0a3a/System.Management.dll
---
SQLEditors
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Co
mmon7/IDE/SQLEditors.DLL
---
Microsoft.VisualStudio.TextManager.Interop
Assembly Version: 7.1.40304.0
Win32 Version: 7.0.4054
CodeBase:
file:///C:/WINDOWS/assembly/GAC/Microsoft.VisualStudio.TextManager.Interop/7
.1.40304.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.TextManager.Interop.dll
---
Microsoft.SqlServer.GridControl
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.GridControl/9.0.242
.0__89845dcd8080cc91/Microsoft.SqlServer.GridControl.dll
---
Microsoft.SqlServerCe.Client
Assembly Version: 9.0.242.0
Win32 Version: 3.0.5207.0
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Co
mmon7/IDE/Microsoft.SqlServerCe.Client.DLL
---
SqlManagerUI
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Co
mmon7/IDE/SqlManagerUI.DLL
---
Microsoft.AnalysisServices
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.AnalysisServices/9.0.242.0__8
9845dcd8080cc91/Microsoft.AnalysisServices.dll
---
Microsoft.SqlServer.DlgGrid
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.DlgGrid/9.0.242.0__
89845dcd8080cc91/Microsoft.SqlServer.DlgGrid.dll
---
Microsoft.SqlServer.DataStorage
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.DataStorage/9.0.242
.0__89845dcd8080cc91/Microsoft.SqlServer.DataStorage.dll
---
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.Philip Orleans wrote:

> I get this blow up and can reproduce it at will.
> I am not going to pay to report a bug.
> I also have another problem with replication. The wizard fails with a
> message saying" invalid column name "options"", but I don't gave any colum
n
> named options in any table or view.
> philip_38@.hotmail.com.
>
The support policy says that MS doesn't charge for bug reports (they
refund your advance charges). You can also file bugs online at the
Product Feedback Centre:
http://lab.msdn.microsoft.com/productfeedback/
David Portas
SQL Server MVP
--

Browsing for Publication error message

I have setup everything from my domain to the dmz following the document from Replication Answers.com "Replication Across Non-Trusted Domains or Using the Internet"
When setting up the anonymous pull subscription, browsing for the DMZ publication, I see the DMZ server (Publisher) but when I click the (+) to view publications I am receiving the error message;
"Could not obtain information about Windows NT group / user 'DOMAIN NAME/SQLAdministrator' "
This is the account that runs my Sql Server Agent of the sql server in the domain (The Subscriber)
I don't want to use this account, the DMZ server is a part of the domain!!!! I have setup a sql account on both the domain sql server & the dmz sql server.
What am I missing? Where would it be retrieving this account?
I feel like I am so close. I was actually able to create a subscription by using Hilary's book & scripts from QA (But couldn't get the Agent to start - Start/Stop Agent were grayed out)
JLS
I tried yet another approach...
I pulled the initial snapshot folder off the publisher & put it on the subscriber. In the subscription properties, I told it to look in this folder on the subscriber, but I get an error message that the process could not read the file.
I'm just trying everything & I think I'm down to my problem has to do with the initial snapshot. PLEASE shove me in the right direction....
"JLS" <jlshoop@.hotmail.com> wrote in message news:OvacGx39FHA.2616@.TK2MSFTNGP15.phx.gbl...
I have setup everything from my domain to the dmz following the document from Replication Answers.com "Replication Across Non-Trusted Domains or Using the Internet"
When setting up the anonymous pull subscription, browsing for the DMZ publication, I see the DMZ server (Publisher) but when I click the (+) to view publications I am receiving the error message;
"Could not obtain information about Windows NT group / user 'DOMAIN NAME/SQLAdministrator' "
This is the account that runs my Sql Server Agent of the sql server in the domain (The Subscriber)
I don't want to use this account, the DMZ server is a part of the domain!!!! I have setup a sql account on both the domain sql server & the dmz sql server.
What am I missing? Where would it be retrieving this account?
I feel like I am so close. I was actually able to create a subscription by using Hilary's book & scripts from QA (But couldn't get the Agent to start - Start/Stop Agent were grayed out)
JLS
|||can you try a nosync?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"JLS" <jlshoop@.hotmail.com> wrote in message
news:ebk7Zx49FHA.1996@.TK2MSFTNGP10.phx.gbl...
I tried yet another approach...
I pulled the initial snapshot folder off the publisher & put it on the
subscriber. In the subscription properties, I told it to look in this
folder on the subscriber, but I get an error message that the process could
not read the file.
I'm just trying everything & I think I'm down to my problem has to do with
the initial snapshot. PLEASE shove me in the right direction....
"JLS" <jlshoop@.hotmail.com> wrote in message
news:OvacGx39FHA.2616@.TK2MSFTNGP15.phx.gbl...
I have setup everything from my domain to the dmz following the document
from Replication Answers.com "Replication Across Non-Trusted Domains or
Using the Internet"
When setting up the anonymous pull subscription, browsing for the DMZ
publication, I see the DMZ server (Publisher) but when I click the (+) to
view publications I am receiving the error message;
"Could not obtain information about Windows NT group / user 'DOMAIN
NAME/SQLAdministrator' "
This is the account that runs my Sql Server Agent of the sql server in the
domain (The Subscriber)
I don't want to use this account, the DMZ server is a part of the
domain!!!! I have setup a sql account on both the domain sql server & the
dmz sql server.
What am I missing? Where would it be retrieving this account?
I feel like I am so close. I was actually able to create a subscription
by using Hilary's book & scripts from QA (But couldn't get the Agent to
start - Start/Stop Agent were grayed out)
JLS
|||At this point I'll try anything!!!!!!!!!!
What do you mean? Where do I try a nosync?
JUDE
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message news:OXtGtM79FHA.3804@.TK2MSFTNGP14.phx.gbl...
can you try a nosync?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"JLS" <jlshoop@.hotmail.com> wrote in message
news:ebk7Zx49FHA.1996@.TK2MSFTNGP10.phx.gbl...
I tried yet another approach...
I pulled the initial snapshot folder off the publisher & put it on the
subscriber. In the subscription properties, I told it to look in this
folder on the subscriber, but I get an error message that the process could
not read the file.
I'm just trying everything & I think I'm down to my problem has to do with
the initial snapshot. PLEASE shove me in the right direction....
"JLS" <jlshoop@.hotmail.com> wrote in message
news:OvacGx39FHA.2616@.TK2MSFTNGP15.phx.gbl...
I have setup everything from my domain to the dmz following the document
from Replication Answers.com "Replication Across Non-Trusted Domains or
Using the Internet"
When setting up the anonymous pull subscription, browsing for the DMZ
publication, I see the DMZ server (Publisher) but when I click the (+) to
view publications I am receiving the error message;
"Could not obtain information about Windows NT group / user 'DOMAIN
NAME/SQLAdministrator' "
This is the account that runs my Sql Server Agent of the sql server in the
domain (The Subscriber)
I don't want to use this account, the DMZ server is a part of the
domain!!!! I have setup a sql account on both the domain sql server & the
dmz sql server.
What am I missing? Where would it be retrieving this account?
I feel like I am so close. I was actually able to create a subscription
by using Hilary's book & scripts from QA (But couldn't get the Agent to
start - Start/Stop Agent were grayed out)
JLS
|||Hi Jude,
While using nosync subscription is a perfectly valid option, the problem that your experienced seems to be the kind that is relatively straightforward to resolve. If I understand the situation correctly, you have manually copied the snapshot files to a different location on the subscriber and attempted to apply the snapshot from the new location via the use of the alternate snapshot folder property of the pull subscription. One non-intuitive quirk that typically catches people off-guard is to set the alternate snapshot location directly to where the snapshot files are rather than to where the unc or ftp folder is. That is, you need to have the <unc|ftp>\<Publisher>_<PublisherDB>_<Publication>\ <timestamp>\<snapshot files> folder structure underneath your alternate snapshot folder. So, if you manually copy the snapshot files around, you would need to recreate the same folder structure that I mention previously in your target location and then point the alternate snapshot folder to the "root" of that sub-structure. I would be interested to know if your scenario has more twists than what I expected.
-Raymond
"JLS" <judes@.email.uophx.edu> wrote in message news:%23i5x8JV%23FHA.4092@.TK2MSFTNGP10.phx.gbl...
At this point I'll try anything!!!!!!!!!!
What do you mean? Where do I try a nosync?
JUDE
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message news:OXtGtM79FHA.3804@.TK2MSFTNGP14.phx.gbl...
can you try a nosync?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"JLS" <jlshoop@.hotmail.com> wrote in message
news:ebk7Zx49FHA.1996@.TK2MSFTNGP10.phx.gbl...
I tried yet another approach...
I pulled the initial snapshot folder off the publisher & put it on the
subscriber. In the subscription properties, I told it to look in this
folder on the subscriber, but I get an error message that the process could
not read the file.
I'm just trying everything & I think I'm down to my problem has to do with
the initial snapshot. PLEASE shove me in the right direction....
"JLS" <jlshoop@.hotmail.com> wrote in message
news:OvacGx39FHA.2616@.TK2MSFTNGP15.phx.gbl...
I have setup everything from my domain to the dmz following the document
from Replication Answers.com "Replication Across Non-Trusted Domains or
Using the Internet"
When setting up the anonymous pull subscription, browsing for the DMZ
publication, I see the DMZ server (Publisher) but when I click the (+) to
view publications I am receiving the error message;
"Could not obtain information about Windows NT group / user 'DOMAIN
NAME/SQLAdministrator' "
This is the account that runs my Sql Server Agent of the sql server in the
domain (The Subscriber)
I don't want to use this account, the DMZ server is a part of the
domain!!!! I have setup a sql account on both the domain sql server & the
dmz sql server.
What am I missing? Where would it be retrieving this account?
I feel like I am so close. I was actually able to create a subscription
by using Hilary's book & scripts from QA (But couldn't get the Agent to
start - Start/Stop Agent were grayed out)
JLS
|||Raymond,
Thank you for this answer, I am going to check to make sure I have my alternate snapshot folder set as you suggest.
If I may impose, when browsing for the publication on the DMZ to setup an anonymous pull subscription, why would I receive an error message about the domain account on the Subscriber that runs the SQL Server Agent service?
Why is it referring to this account at all?
Certainly both servers Sql Server agent accounts do not have to be the same, especially when one of the servers is out on the net & not even on the domain?
Any light you can shed on this will be greatly appreciated.
Thanx!!!!
Jude
"Raymond Mak [MSFT]" <rmak@.online.microsoft.com> wrote in message news:uw5NrKc%23FHA.912@.TK2MSFTNGP11.phx.gbl...
Hi Jude,
While using nosync subscription is a perfectly valid option, the problem that your experienced seems to be the kind that is relatively straightforward to resolve. If I understand the situation correctly, you have manually copied the snapshot files to a different location on the subscriber and attempted to apply the snapshot from the new location via the use of the alternate snapshot folder property of the pull subscription. One non-intuitive quirk that typically catches people off-guard is to set the alternate snapshot location directly to where the snapshot files are rather than to where the unc or ftp folder is. That is, you need to have the <unc|ftp>\<Publisher>_<PublisherDB>_<Publication>\ <timestamp>\<snapshot files> folder structure underneath your alternate snapshot folder. So, if you manually copy the snapshot files around, you would need to recreate the same folder structure that I mention previously in your target location and then point the alternate snapshot folder to the "root" of that sub-structure. I would be interested to know if your scenario has more twists than what I expected.
-Raymond
"JLS" <judes@.email.uophx.edu> wrote in message news:%23i5x8JV%23FHA.4092@.TK2MSFTNGP10.phx.gbl...
At this point I'll try anything!!!!!!!!!!
What do you mean? Where do I try a nosync?
JUDE
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message news:OXtGtM79FHA.3804@.TK2MSFTNGP14.phx.gbl...
can you try a nosync?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"JLS" <jlshoop@.hotmail.com> wrote in message
news:ebk7Zx49FHA.1996@.TK2MSFTNGP10.phx.gbl...
I tried yet another approach...
I pulled the initial snapshot folder off the publisher & put it on the
subscriber. In the subscription properties, I told it to look in this
folder on the subscriber, but I get an error message that the process could
not read the file.
I'm just trying everything & I think I'm down to my problem has to do with
the initial snapshot. PLEASE shove me in the right direction....
"JLS" <jlshoop@.hotmail.com> wrote in message
news:OvacGx39FHA.2616@.TK2MSFTNGP15.phx.gbl...
I have setup everything from my domain to the dmz following the document
from Replication Answers.com "Replication Across Non-Trusted Domains or
Using the Internet"
When setting up the anonymous pull subscription, browsing for the DMZ
publication, I see the DMZ server (Publisher) but when I click the (+) to
view publications I am receiving the error message;
"Could not obtain information about Windows NT group / user 'DOMAIN
NAME/SQLAdministrator' "
This is the account that runs my Sql Server Agent of the sql server in the
domain (The Subscriber)
I don't want to use this account, the DMZ server is a part of the
domain!!!! I have setup a sql account on both the domain sql server & the
dmz sql server.
What am I missing? Where would it be retrieving this account?
I feel like I am so close. I was actually able to create a subscription
by using Hilary's book & scripts from QA (But couldn't get the Agent to
start - Start/Stop Agent were grayed out)
JLS
|||Hi Jude,
It is sort of difficult for me to visualize exactly what is going on with the description you gave previously (or any kind of description that you can possibly provide over the newsgroup) but I would guess that the subscriber SQL Server Agent service account was somehow added to the publication access list of the publication on the DMZ. If this is the case then you will likely see the kind of error message that you saw when browsing the publication properties through the UI (which also enumerates entries in the publication acces list). To find out, select from the MSpublication_access table in the distribution database and see if the account for your Subscriber's SQL Server Agent service account shows up. If so, manually removing the row will likely resolve the issue for you.
-Raymond
"JLS" <jlshoop@.hotmail.com> wrote in message news:%23dfKH4c%23FHA.1148@.tk2msftngp13.phx.gbl...
Raymond,
Thank you for this answer, I am going to check to make sure I have my alternate snapshot folder set as you suggest.
If I may impose, when browsing for the publication on the DMZ to setup an anonymous pull subscription, why would I receive an error message about the domain account on the Subscriber that runs the SQL Server Agent service?
Why is it referring to this account at all?
Certainly both servers Sql Server agent accounts do not have to be the same, especially when one of the servers is out on the net & not even on the domain?
Any light you can shed on this will be greatly appreciated.
Thanx!!!!
Jude
"Raymond Mak [MSFT]" <rmak@.online.microsoft.com> wrote in message news:uw5NrKc%23FHA.912@.TK2MSFTNGP11.phx.gbl...
Hi Jude,
While using nosync subscription is a perfectly valid option, the problem that your experienced seems to be the kind that is relatively straightforward to resolve. If I understand the situation correctly, you have manually copied the snapshot files to a different location on the subscriber and attempted to apply the snapshot from the new location via the use of the alternate snapshot folder property of the pull subscription. One non-intuitive quirk that typically catches people off-guard is to set the alternate snapshot location directly to where the snapshot files are rather than to where the unc or ftp folder is. That is, you need to have the <unc|ftp>\<Publisher>_<PublisherDB>_<Publication>\ <timestamp>\<snapshot files> folder structure underneath your alternate snapshot folder. So, if you manually copy the snapshot files around, you would need to recreate the same folder structure that I mention previously in your target location and then point the alternate snapshot folder to the "root" of that sub-structure. I would be interested to know if your scenario has more twists than what I expected.
-Raymond
"JLS" <judes@.email.uophx.edu> wrote in message news:%23i5x8JV%23FHA.4092@.TK2MSFTNGP10.phx.gbl...
At this point I'll try anything!!!!!!!!!!
What do you mean? Where do I try a nosync?
JUDE
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message news:OXtGtM79FHA.3804@.TK2MSFTNGP14.phx.gbl...
can you try a nosync?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"JLS" <jlshoop@.hotmail.com> wrote in message
news:ebk7Zx49FHA.1996@.TK2MSFTNGP10.phx.gbl...
I tried yet another approach...
I pulled the initial snapshot folder off the publisher & put it on the
subscriber. In the subscription properties, I told it to look in this
folder on the subscriber, but I get an error message that the process could
not read the file.
I'm just trying everything & I think I'm down to my problem has to do with
the initial snapshot. PLEASE shove me in the right direction....
"JLS" <jlshoop@.hotmail.com> wrote in message
news:OvacGx39FHA.2616@.TK2MSFTNGP15.phx.gbl...
I have setup everything from my domain to the dmz following the document
from Replication Answers.com "Replication Across Non-Trusted Domains or
Using the Internet"
When setting up the anonymous pull subscription, browsing for the DMZ
publication, I see the DMZ server (Publisher) but when I click the (+) to
view publications I am receiving the error message;
"Could not obtain information about Windows NT group / user 'DOMAIN
NAME/SQLAdministrator' "
This is the account that runs my Sql Server Agent of the sql server in the
domain (The Subscriber)
I don't want to use this account, the DMZ server is a part of the
domain!!!! I have setup a sql account on both the domain sql server & the
dmz sql server.
What am I missing? Where would it be retrieving this account?
I feel like I am so close. I was actually able to create a subscription
by using Hilary's book & scripts from QA (But couldn't get the Agent to
start - Start/Stop Agent were grayed out)
JLS
|||Sorry for the cryptic description, I posted in another thread describing my problem in detail, so let me do that again with you & perhaps you can 'see' where I am going wrong.
Subscriber = On my domain
DMZ SQL Server = Not on my domain (1 way trust is setup)
There is a firewall involved here (My Network Admin has VERY reluctantly setup rules on the firewall)
================================================== ================================================== ==========
The Subscriber can connect to the Publisher in the DMZ, no problem. As a matter of fact, this particular Subscriber server is publishing to this DMZ server (One way trust is working fine)
I have the alias set & I have an entry in the hosts file for this DMZ server.
I have the publication setup to allow anonymous subscriptions.
Here's what I am down to when I try to setup the Pull Subscription at the Subscriber, from the publication on the DMZ server.
I get an error message about not being able to retrieve info about publications on the DMZ Server AND I get an error message about not being able to retrieve info about the Domain account that is the Service startup account for Sql Agent on the Subscriber. I don't want to use this domain account anyway, I have the publication setup to use a Sql Account that I created specifically for this replication.
Why would it be trying to use the Sql Agent Service Account, and not REPLDMZ sql account I setup on both boxes?
================================================== ================================================== ===========
So, I tried to set everything up by using scripts on the Subscriber.
exec sp_addpullsubscription
@.publisher = 'MARKYMARK',
@.publisher_db = 'SNN',
@.publication = 'SNN',
@.independent_agent = 'True',
@.subscription_type = 'anonymous',
@.update_mode = 'read only'
exec sp_addpullsubscription_agent
@.publisher = 'MARKYMARK',
@.publisher_db = 'SNN',
@.publication = 'SNN',
@.distributor = 'MARKYMARK',
@.subscriber_security_mode = 1,
@.distributor_security_mode = 1,
@.subscriber_login = 'repldmz',
@.subscriber_password = 'insert password here'
I get a connection failure when I try to start synchronizing, it says it can't connect to the distributor on the DMZ server & appears to be trying to connect with the Subscriber domain account that runs sql agent on the subscriber.
I haven't setup replication using scripts before, so this was just a shot in the dark since I cannot browse the DMZ publications from EM.
Is this a better description of my issue? I feel like I'm really close to getting this anonymous pull setup, but one piece of the puzzle is missing?
Jude
"Raymond Mak [MSFT]" <rmak@.online.microsoft.com> wrote in message news:ODHM0Jd%23FHA.740@.TK2MSFTNGP11.phx.gbl...
Hi Jude,
It is sort of difficult for me to visualize exactly what is going on with the description you gave previously (or any kind of description that you can possibly provide over the newsgroup) but I would guess that the subscriber SQL Server Agent service account was somehow added to the publication access list of the publication on the DMZ. If this is the case then you will likely see the kind of error message that you saw when browsing the publication properties through the UI (which also enumerates entries in the publication acces list). To find out, select from the MSpublication_access table in the distribution database and see if the account for your Subscriber's SQL Server Agent service account shows up. If so, manually removing the row will likely resolve the issue for you.
-Raymond
"JLS" <jlshoop@.hotmail.com> wrote in message news:%23dfKH4c%23FHA.1148@.tk2msftngp13.phx.gbl...
Raymond,
Thank you for this answer, I am going to check to make sure I have my alternate snapshot folder set as you suggest.
If I may impose, when browsing for the publication on the DMZ to setup an anonymous pull subscription, why would I receive an error message about the domain account on the Subscriber that runs the SQL Server Agent service?
Why is it referring to this account at all?
Certainly both servers Sql Server agent accounts do not have to be the same, especially when one of the servers is out on the net & not even on the domain?
Any light you can shed on this will be greatly appreciated.
Thanx!!!!
Jude
"Raymond Mak [MSFT]" <rmak@.online.microsoft.com> wrote in message news:uw5NrKc%23FHA.912@.TK2MSFTNGP11.phx.gbl...
Hi Jude,
While using nosync subscription is a perfectly valid option, the problem that your experienced seems to be the kind that is relatively straightforward to resolve. If I understand the situation correctly, you have manually copied the snapshot files to a different location on the subscriber and attempted to apply the snapshot from the new location via the use of the alternate snapshot folder property of the pull subscription. One non-intuitive quirk that typically catches people off-guard is to set the alternate snapshot location directly to where the snapshot files are rather than to where the unc or ftp folder is. That is, you need to have the <unc|ftp>\<Publisher>_<PublisherDB>_<Publication>\ <timestamp>\<snapshot files> folder structure underneath your alternate snapshot folder. So, if you manually copy the snapshot files around, you would need to recreate the same folder structure that I mention previously in your target location and then point the alternate snapshot folder to the "root" of that sub-structure. I would be interested to know if your scenario has more twists than what I expected.
-Raymond
"JLS" <judes@.email.uophx.edu> wrote in message news:%23i5x8JV%23FHA.4092@.TK2MSFTNGP10.phx.gbl...
At this point I'll try anything!!!!!!!!!!
What do you mean? Where do I try a nosync?
JUDE
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message news:OXtGtM79FHA.3804@.TK2MSFTNGP14.phx.gbl...
can you try a nosync?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"JLS" <jlshoop@.hotmail.com> wrote in message
news:ebk7Zx49FHA.1996@.TK2MSFTNGP10.phx.gbl...
I tried yet another approach...
I pulled the initial snapshot folder off the publisher & put it on the
subscriber. In the subscription properties, I told it to look in this
folder on the subscriber, but I get an error message that the process could
not read the file.
I'm just trying everything & I think I'm down to my problem has to do with
the initial snapshot. PLEASE shove me in the right direction....
"JLS" <jlshoop@.hotmail.com> wrote in message
news:OvacGx39FHA.2616@.TK2MSFTNGP15.phx.gbl...
I have setup everything from my domain to the dmz following the document
from Replication Answers.com "Replication Across Non-Trusted Domains or
Using the Internet"
When setting up the anonymous pull subscription, browsing for the DMZ
publication, I see the DMZ server (Publisher) but when I click the (+) to
view publications I am receiving the error message;
"Could not obtain information about Windows NT group / user 'DOMAIN
NAME/SQLAdministrator' "
This is the account that runs my Sql Server Agent of the sql server in the
domain (The Subscriber)
I don't want to use this account, the DMZ server is a part of the
domain!!!! I have setup a sql account on both the domain sql server & the
dmz sql server.
What am I missing? Where would it be retrieving this account?
I feel like I am so close. I was actually able to create a subscription
by using Hilary's book & scripts from QA (But couldn't get the Agent to
start - Start/Stop Agent were grayed out)
JLS
|||Did you see the Subscriber's SQL Server Agent account in MSpublication_access?
-Raymond
"JLS" <jlshoop@.hotmail.com> wrote in message news:u50SRVd%23FHA.2704@.TK2MSFTNGP15.phx.gbl...
Sorry for the cryptic description, I posted in another thread describing my problem in detail, so let me do that again with you & perhaps you can 'see' where I am going wrong.
Subscriber = On my domain
DMZ SQL Server = Not on my domain (1 way trust is setup)
There is a firewall involved here (My Network Admin has VERY reluctantly setup rules on the firewall)
================================================== ================================================== ==========
The Subscriber can connect to the Publisher in the DMZ, no problem. As a matter of fact, this particular Subscriber server is publishing to this DMZ server (One way trust is working fine)
I have the alias set & I have an entry in the hosts file for this DMZ server.
I have the publication setup to allow anonymous subscriptions.
Here's what I am down to when I try to setup the Pull Subscription at the Subscriber, from the publication on the DMZ server.
I get an error message about not being able to retrieve info about publications on the DMZ Server AND I get an error message about not being able to retrieve info about the Domain account that is the Service startup account for Sql Agent on the Subscriber. I don't want to use this domain account anyway, I have the publication setup to use a Sql Account that I created specifically for this replication.
Why would it be trying to use the Sql Agent Service Account, and not REPLDMZ sql account I setup on both boxes?
================================================== ================================================== ===========
So, I tried to set everything up by using scripts on the Subscriber.
exec sp_addpullsubscription
@.publisher = 'MARKYMARK',
@.publisher_db = 'SNN',
@.publication = 'SNN',
@.independent_agent = 'True',
@.subscription_type = 'anonymous',
@.update_mode = 'read only'
exec sp_addpullsubscription_agent
@.publisher = 'MARKYMARK',
@.publisher_db = 'SNN',
@.publication = 'SNN',
@.distributor = 'MARKYMARK',
@.subscriber_security_mode = 1,
@.distributor_security_mode = 1,
@.subscriber_login = 'repldmz',
@.subscriber_password = 'insert password here'
I get a connection failure when I try to start synchronizing, it says it can't connect to the distributor on the DMZ server & appears to be trying to connect with the Subscriber domain account that runs sql agent on the subscriber.
I haven't setup replication using scripts before, so this was just a shot in the dark since I cannot browse the DMZ publications from EM.
Is this a better description of my issue? I feel like I'm really close to getting this anonymous pull setup, but one piece of the puzzle is missing?
Jude
"Raymond Mak [MSFT]" <rmak@.online.microsoft.com> wrote in message news:ODHM0Jd%23FHA.740@.TK2MSFTNGP11.phx.gbl...
Hi Jude,
It is sort of difficult for me to visualize exactly what is going on with the description you gave previously (or any kind of description that you can possibly provide over the newsgroup) but I would guess that the subscriber SQL Server Agent service account was somehow added to the publication access list of the publication on the DMZ. If this is the case then you will likely see the kind of error message that you saw when browsing the publication properties through the UI (which also enumerates entries in the publication acces list). To find out, select from the MSpublication_access table in the distribution database and see if the account for your Subscriber's SQL Server Agent service account shows up. If so, manually removing the row will likely resolve the issue for you.
-Raymond
"JLS" <jlshoop@.hotmail.com> wrote in message news:%23dfKH4c%23FHA.1148@.tk2msftngp13.phx.gbl...
Raymond,
Thank you for this answer, I am going to check to make sure I have my alternate snapshot folder set as you suggest.
If I may impose, when browsing for the publication on the DMZ to setup an anonymous pull subscription, why would I receive an error message about the domain account on the Subscriber that runs the SQL Server Agent service?
Why is it referring to this account at all?
Certainly both servers Sql Server agent accounts do not have to be the same, especially when one of the servers is out on the net & not even on the domain?
Any light you can shed on this will be greatly appreciated.
Thanx!!!!
Jude
"Raymond Mak [MSFT]" <rmak@.online.microsoft.com> wrote in message news:uw5NrKc%23FHA.912@.TK2MSFTNGP11.phx.gbl...
Hi Jude,
While using nosync subscription is a perfectly valid option, the problem that your experienced seems to be the kind that is relatively straightforward to resolve. If I understand the situation correctly, you have manually copied the snapshot files to a different location on the subscriber and attempted to apply the snapshot from the new location via the use of the alternate snapshot folder property of the pull subscription. One non-intuitive quirk that typically catches people off-guard is to set the alternate snapshot location directly to where the snapshot files are rather than to where the unc or ftp folder is. That is, you need to have the <unc|ftp>\<Publisher>_<PublisherDB>_<Publication>\ <timestamp>\<snapshot files> folder structure underneath your alternate snapshot folder. So, if you manually copy the snapshot files around, you would need to recreate the same folder structure that I mention previously in your target location and then point the alternate snapshot folder to the "root" of that sub-structure. I would be interested to know if your scenario has more twists than what I expected.
-Raymond
"JLS" <judes@.email.uophx.edu> wrote in message news:%23i5x8JV%23FHA.4092@.TK2MSFTNGP10.phx.gbl...
At this point I'll try anything!!!!!!!!!!
What do you mean? Where do I try a nosync?
JUDE
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message news:OXtGtM79FHA.3804@.TK2MSFTNGP14.phx.gbl...
can you try a nosync?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"JLS" <jlshoop@.hotmail.com> wrote in message
news:ebk7Zx49FHA.1996@.TK2MSFTNGP10.phx.gbl...
I tried yet another approach...
I pulled the initial snapshot folder off the publisher & put it on the
subscriber. In the subscription properties, I told it to look in this
folder on the subscriber, but I get an error message that the process could
not read the file.
I'm just trying everything & I think I'm down to my problem has to do with
the initial snapshot. PLEASE shove me in the right direction....
"JLS" <jlshoop@.hotmail.com> wrote in message
news:OvacGx39FHA.2616@.TK2MSFTNGP15.phx.gbl...
I have setup everything from my domain to the dmz following the document
from Replication Answers.com "Replication Across Non-Trusted Domains or
Using the Internet"
When setting up the anonymous pull subscription, browsing for the DMZ
publication, I see the DMZ server (Publisher) but when I click the (+) to
view publications I am receiving the error message;
"Could not obtain information about Windows NT group / user 'DOMAIN
NAME/SQLAdministrator' "
This is the account that runs my Sql Server Agent of the sql server in the
domain (The Subscriber)
I don't want to use this account, the DMZ server is a part of the
domain!!!! I have setup a sql account on both the domain sql server & the
dmz sql server.
What am I missing? Where would it be retrieving this account?
I feel like I am so close. I was actually able to create a subscription
by using Hilary's book & scripts from QA (But couldn't get the Agent to
start - Start/Stop Agent were grayed out)
JLS
|||No, the publication access list has the sql account I created specifically for this replication (repldmz), the sa account, and distributor_admin listed.
Jude
"Raymond Mak [MSFT]" <rmak@.online.microsoft.com> wrote in message news:%23wnKBed%23FHA.472@.TK2MSFTNGP15.phx.gbl...
Did you see the Subscriber's SQL Server Agent account in MSpublication_access?
-Raymond
"JLS" <jlshoop@.hotmail.com> wrote in message news:u50SRVd%23FHA.2704@.TK2MSFTNGP15.phx.gbl...
Sorry for the cryptic description, I posted in another thread describing my problem in detail, so let me do that again with you & perhaps you can 'see' where I am going wrong.
Subscriber = On my domain
DMZ SQL Server = Not on my domain (1 way trust is setup)
There is a firewall involved here (My Network Admin has VERY reluctantly setup rules on the firewall)
================================================== ================================================== ==========
The Subscriber can connect to the Publisher in the DMZ, no problem. As a matter of fact, this particular Subscriber server is publishing to this DMZ server (One way trust is working fine)
I have the alias set & I have an entry in the hosts file for this DMZ server.
I have the publication setup to allow anonymous subscriptions.
Here's what I am down to when I try to setup the Pull Subscription at the Subscriber, from the publication on the DMZ server.
I get an error message about not being able to retrieve info about publications on the DMZ Server AND I get an error message about not being able to retrieve info about the Domain account that is the Service startup account for Sql Agent on the Subscriber. I don't want to use this domain account anyway, I have the publication setup to use a Sql Account that I created specifically for this replication.
Why would it be trying to use the Sql Agent Service Account, and not REPLDMZ sql account I setup on both boxes?
================================================== ================================================== ===========
So, I tried to set everything up by using scripts on the Subscriber.
exec sp_addpullsubscription
@.publisher = 'MARKYMARK',
@.publisher_db = 'SNN',
@.publication = 'SNN',
@.independent_agent = 'True',
@.subscription_type = 'anonymous',
@.update_mode = 'read only'
exec sp_addpullsubscription_agent
@.publisher = 'MARKYMARK',
@.publisher_db = 'SNN',
@.publication = 'SNN',
@.distributor = 'MARKYMARK',
@.subscriber_security_mode = 1,
@.distributor_security_mode = 1,
@.subscriber_login = 'repldmz',
@.subscriber_password = 'insert password here'
I get a connection failure when I try to start synchronizing, it says it can't connect to the distributor on the DMZ server & appears to be trying to connect with the Subscriber domain account that runs sql agent on the subscriber.
I haven't setup replication using scripts before, so this was just a shot in the dark since I cannot browse the DMZ publications from EM.
Is this a better description of my issue? I feel like I'm really close to getting this anonymous pull setup, but one piece of the puzzle is missing?
Jude
"Raymond Mak [MSFT]" <rmak@.online.microsoft.com> wrote in message news:ODHM0Jd%23FHA.740@.TK2MSFTNGP11.phx.gbl...
Hi Jude,
It is sort of difficult for me to visualize exactly what is going on with the description you gave previously (or any kind of description that you can possibly provide over the newsgroup) but I would guess that the subscriber SQL Server Agent service account was somehow added to the publication access list of the publication on the DMZ. If this is the case then you will likely see the kind of error message that you saw when browsing the publication properties through the UI (which also enumerates entries in the publication acces list). To find out, select from the MSpublication_access table in the distribution database and see if the account for your Subscriber's SQL Server Agent service account shows up. If so, manually removing the row will likely resolve the issue for you.
-Raymond
"JLS" <jlshoop@.hotmail.com> wrote in message news:%23dfKH4c%23FHA.1148@.tk2msftngp13.phx.gbl...
Raymond,
Thank you for this answer, I am going to check to make sure I have my alternate snapshot folder set as you suggest.
If I may impose, when browsing for the publication on the DMZ to setup an anonymous pull subscription, why would I receive an error message about the domain account on the Subscriber that runs the SQL Server Agent service?
Why is it referring to this account at all?
Certainly both servers Sql Server agent accounts do not have to be the same, especially when one of the servers is out on the net & not even on the domain?
Any light you can shed on this will be greatly appreciated.
Thanx!!!!
Jude
"Raymond Mak [MSFT]" <rmak@.online.microsoft.com> wrote in message news:uw5NrKc%23FHA.912@.TK2MSFTNGP11.phx.gbl...
Hi Jude,
While using nosync subscription is a perfectly valid option, the problem that your experienced seems to be the kind that is relatively straightforward to resolve. If I understand the situation correctly, you have manually copied the snapshot files to a different location on the subscriber and attempted to apply the snapshot from the new location via the use of the alternate snapshot folder property of the pull subscription. One non-intuitive quirk that typically catches people off-guard is to set the alternate snapshot location directly to where the snapshot files are rather than to where the unc or ftp folder is. That is, you need to have the <unc|ftp>\<Publisher>_<PublisherDB>_<Publication>\ <timestamp>\<snapshot files> folder structure underneath your alternate snapshot folder. So, if you manually copy the snapshot files around, you would need to recreate the same folder structure that I mention previously in your target location and then point the alternate snapshot folder to the "root" of that sub-structure. I would be interested to know if your scenario has more twists than what I expected.
-Raymond
"JLS" <judes@.email.uophx.edu> wrote in message news:%23i5x8JV%23FHA.4092@.TK2MSFTNGP10.phx.gbl...
At this point I'll try anything!!!!!!!!!!
What do you mean? Where do I try a nosync?
JUDE
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message news:OXtGtM79FHA.3804@.TK2MSFTNGP14.phx.gbl...
can you try a nosync?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"JLS" <jlshoop@.hotmail.com> wrote in message
news:ebk7Zx49FHA.1996@.TK2MSFTNGP10.phx.gbl...
I tried yet another approach...
I pulled the initial snapshot folder off the publisher & put it on the
subscriber. In the subscription properties, I told it to look in this
folder on the subscriber, but I get an error message that the process could
not read the file.
I'm just trying everything & I think I'm down to my problem has to do with
the initial snapshot. PLEASE shove me in the right direction....
"JLS" <jlshoop@.hotmail.com> wrote in message
news:OvacGx39FHA.2616@.TK2MSFTNGP15.phx.gbl...
I have setup everything from my domain to the dmz following the document
from Replication Answers.com "Replication Across Non-Trusted Domains or
Using the Internet"
When setting up the anonymous pull subscription, browsing for the DMZ
publication, I see the DMZ server (Publisher) but when I click the (+) to
view publications I am receiving the error message;
"Could not obtain information about Windows NT group / user 'DOMAIN
NAME/SQLAdministrator' "
This is the account that runs my Sql Server Agent of the sql server in the
domain (The Subscriber)
I don't want to use this account, the DMZ server is a part of the
domain!!!! I have setup a sql account on both the domain sql server & the
dmz sql server.
What am I missing? Where would it be retrieving this account?
I feel like I am so close. I was actually able to create a subscription
by using Hilary's book & scripts from QA (But couldn't get the Agent to
start - Start/Stop Agent were grayed out)
JLS

Browse Replication commands

Hi,
We are trying to setup a two-way replication from STL to China. We
know that the network is very unreliable, and not very good bandwidth.
Inorder to decide if this is feasible, I need to provide information
about how much data will we be replicating everyhour, and how big a
transaction can be in kb.
In transactional replication, when we issue an update or a delete
statement on a table, that affects 100 rows, when the change gets
replicated, will it issue 100 cmds on subscriber or just 1 statement,
that would affect 100 rows. I would like to know if we will be sending
100 statements over the network or just 1.
When I look at distribution agent history, it tells me the no. of cmds
that it transfered and the rate of no. of trans/sec, latency etc... Is
there a way to know the size of the transaction in KB's?
In order to get a good estimate on the size of the data that would be
replicated, can I rely on the size of Tlog backups generated every day?
The database that we plan to replicate is 17GIG, to do an initial
snapshot, it would take a while, is there an easy way to sync up the
database, incase it goes out of sync( for eg: Restore the database, and
start replication).
Thanks for your help.
GG
Tlogs tend to be much larger than the bandwidth consumed by transactional
replication, however this depends on many factors, such as what sort of
indexing optimizations you are doing (which are logged).
I would look at replicating the execution of stored procedures as this will
transform the 100 singletons to a single command.
And yes 100 commands will go across the network. There is no way I know of
to get an idea of the bandwidth requirements.
The best way to deploy the snapshot is from a backup. Change all the
identity cols, constraints, triggers to Not For Replication on the
subscriber.
The best way to resync is to set your history retention to 1 week or so, and
your minimum transaction to 2 days. This way if your subscriber fails, you
can restore from backup (yesterdays) and all the missing transactions will
be automatically backfilled!
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"GG" <gdabbara@.gmail.com> wrote in message
news:1117649116.626833.200590@.g49g2000cwa.googlegr oups.com...
> Hi,
> We are trying to setup a two-way replication from STL to China. We
> know that the network is very unreliable, and not very good bandwidth.
> Inorder to decide if this is feasible, I need to provide information
> about how much data will we be replicating everyhour, and how big a
> transaction can be in kb.
> In transactional replication, when we issue an update or a delete
> statement on a table, that affects 100 rows, when the change gets
> replicated, will it issue 100 cmds on subscriber or just 1 statement,
> that would affect 100 rows. I would like to know if we will be sending
> 100 statements over the network or just 1.
> When I look at distribution agent history, it tells me the no. of cmds
> that it transfered and the rate of no. of trans/sec, latency etc... Is
> there a way to know the size of the transaction in KB's?
> In order to get a good estimate on the size of the data that would be
> replicated, can I rely on the size of Tlog backups generated every day?
> The database that we plan to replicate is 17GIG, to do an initial
> snapshot, it would take a while, is there an easy way to sync up the
> database, incase it goes out of sync( for eg: Restore the database, and
> start replication).
> Thanks for your help.
> GG
>
|||I am sorry! What does index optimizations mean? We do use indexes
extensively, as we are replicating an OLTP system. We will be
replicating the whole database, and we will set notfor replication
options on triggers and identity columns. As we are replicating the
entire database, do you think Tlog activity should reflect the size of
replicated data?
Yes, we will setup to use stored procs instead of TSQL statements. How
would they transform 100 singletons to one command. I thought they are
effecient because they are cached and the parameters are passed in as
binary values.
When you said restore from the backup if subscriber goes out of sync,
did you mean the subscriber database backup or the publisher? If it
is subscriber's backup, then that would be good, that way we don't have
to mail in a copy of our backup everytime something goes out of sync.
Looks like this might be better than having to compress snapshot files,
and send it to other location.
One question though, how does it know what transactions to apply to the
subscriber, because my subscriber could have gone out of sync say at
10:00AM, and then when If I restore the subscriber from previous
night's backup, how does it know from when to start applying the
transactions. Does it read the Tlogs to find the LSN or something?
Thanks a lot of your reply.
GG