Re: Index Tuning Wizard and Transactional Replication

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Hilary Cotter (hilary.cotter_at_gmail.com)
Date: 10/05/04

  • Next message: larry: "Missing Snapshot Agents"
    Date: Tue, 5 Oct 2004 11:10:10 -0400
    
    

    look in %windir%\system32 for recent *.err messages

    -- 
    Hilary Cotter
    Looking for a SQL Server replication book?
    http://www.nwsu.com/0974973602.html
    "Marcio G Macedo" <MarcioGMacedo@discussions.microsoft.com> wrote in message
    news:D1C5AB88-BE5A-49B3-95B3-F42369CA1E37@microsoft.com...
    > Hi Hilary:
    >
    > It is an ERROR (the red cross).
    >
    > There are no other messages or explanations at all.....not even a title
    just
    > the message.
    >
    > I've been breacking my head for almost one month trying to figure it out .
    >
    > Thanks for your reply.
    >
    > "Hilary Cotter" wrote:
    >
    > > can you add the entire error and warning events and see which one
    generates
    > > a failure/error/warning?
    > >
    > > -- 
    > > Hilary Cotter
    > > Looking for a SQL Server replication book?
    > > http://www.nwsu.com/0974973602.html
    > >
    > >
    > > "Marcio G Macedo" <MarcioGMacedo@discussions.microsoft.com> wrote in
    message
    > > news:477C556B-CB15-44B6-A37B-193E429B5AA8@microsoft.com...
    > > > Good Morning!
    > > >
    > > > Running the Index Tuning Wizard against a database that is the
    Publisher
    > > in
    > > > a Transactional Replication, returns, "An error occurred trying to
    execute
    > > a
    > > > SQL statement," when analyzing the database and the workload.
    > > >
    > > > Running the same statement against a Subscriber or a database that is
    not
    > > > being used for replication, the Wizard runs without any issue.
    > > >
    > > > The Publisher is located in a different Server (but in the same
    machine)
    > > > from the Subscriber and the isolated database and the error occurs for
    any
    > > > statement.
    > > >
    > > > No other issue had been reported in the Publisher database, which is
    used
    > > in
    > > > our production environment.
    > > >
    > > > Any thoughts, recommendations, lectures, or articles will be great
    > > > appreciated.
    > > >
    > > > -- 
    > > > Thank you,
    > > > Marcio G Macedo
    > >
    > >
    > >
    

  • Next message: larry: "Missing Snapshot Agents"

    Relevant Pages

    • Re: Merge Replication Error: "The Process could not enumerate changes at the Subscriber"
      ... Hilary Cotter ... Director of Text Mining and Database Strategy ... Looking for a SQL Server replication book? ...
      (microsoft.public.sqlserver.replication)
    • Re: Change QueryTimeout
      ... It could be transactions queued in the distribution database. ... Looking for a SQL Server replication book? ... "Hilary Cotter" wrote: ... I cannot get to agent properties because the subscribers are ...
      (microsoft.public.sqlserver.replication)
    • Re: full text body search not finding all results
      ... I looked under the database tables and I found this information: ... "Hilary Cotter" wrote: ... Looking for a SQL Server replication book? ... Looking for a FAQ on Indexing Services/SQL FTS ...
      (microsoft.public.sqlserver.fulltext)
    • Re: 2 Merge Publications using same Source Tables, is it possible?
      ... "L Anthony Johnson" wrote in message ... > "Hilary Cotter" wrote in message ... >> table to one table with the same name in the subscription database. ... >> Looking for a book on SQL Server replication? ...
      (microsoft.public.sqlserver.replication)
    • Re: Log Reader Agent remains after removing replication
      ... Looking for a SQL Server replication book? ... "Hilary Cotter" wrote: ... database to a new name and setup replication for the renamed database. ... original Log Reader and Distribution agents still remain and show error ...
      (microsoft.public.sqlserver.replication)