Re: Frequent use of attach and detach

From: Greg Linwood (g_linwoodQhotmail.com)
Date: 03/17/04

  • Next message: David Pless: "Re: Error 7201: Could not execute procedure on remote server "repl_distributor' because SQL Server is not configured for remote access."
    Date: Wed, 17 Mar 2004 14:41:34 +1100
    
    

    Hi Terris.

    I'm inclined to agree with you on this as you're right - attach / detach is
    a feature that should work regardless of usage frequency.

    However, Replication stands out to me as an obvious alternative to your
    solution. Have you considered it? If so, why was it discarded? I'd suggest
    that replication might be your best bet as it's purpose built for scenarios
    like this and if used, would help define an architecture for the solution
    that is easier to maintain. I say this due to familiarity with DBAs
    generally with replication and also availability of tools for managing
    replicated processes - you'd also need to build admin tools capable of
    monitoring your solution..

    HTH

    Regards,
    Greg Linwood
    SQL Server MVP

    "Terris Linenbach" <nospam@nospam.com> wrote in message
    news:%23SdL896CEHA.3132@TK2MSFTNGP11.phx.gbl...
    > We are considering an architecture in which "detach" and "attach" are used
    > on a daily, automated basis for about 50 databases, each containing about
    10
    > gigs of data.
    >
    > We use network attached storage (Network Applicance).
    >
    > We want to have a farm of load servers for a data warehouse. When a load
    > server in the farm is available, it "attach"es a local database to a raw
    > database file "F" and loads data. After loading data, the database is
    > detached. Another server later detaches its local database file and
    > attaches to file "F."
    >
    > This scheme frees personnel from manually configuring servers around
    > unpredictable load times. It is virtually impossible for a human to
    > optimally allocate and schedule machines for this task.
    >
    > We contacted MS tech support to get their feedback and they don't advise
    > such a strategy. The consequences of frequent use of "attach" and
    "detach"
    > are unknown, according to tech support. This seems a little strange to
    me,
    > since "attach" and "detach" are real features.
    >
    > Has anyone tried to do something like this?
    >
    > Thank you.
    >
    >


  • Next message: David Pless: "Re: Error 7201: Could not execute procedure on remote server "repl_distributor' because SQL Server is not configured for remote access."

    Relevant Pages

    • Re: Migration replication jobs
      ... You will be unable to detach replicated databases. ... then drop the publications, unpublish the databases and detach them. ... them on the new server, run the publication script and do a non sync. ... Looking for a SQL Server replication book? ...
      (microsoft.public.sqlserver.replication)
    • Re: SBS 2003 and Replication Errors with Remote DC
      ... I just promoted the remote DC last week, so I still have time to solve the replication issues. ... Domain Controller Diagnosis ... Connecting to directory service on server alpha. ... Performing upstream analysis. ...
      (microsoft.public.windows.server.sbs)
    • Re: SBS 2003 and Replication Errors with Remote DC
      ... alpha server as soon as you can to get things going. ... A simple DNS replication test is to create a host record in the SBS server ... Domain Controller Diagnosis ...
      (microsoft.public.windows.server.sbs)
    • Re: SBS 2003 and Replication Errors with Remote DC
      ... I did make the changes that you suggested on the DNS of my alpha server and rebooted. ... I did run the simple DNS test that you suggested by adding a host record to my SBS server. ... A simple DNS replication test is to create a host record in the SBS server and wait till it shows up in the remote server. ...
      (microsoft.public.windows.server.sbs)
    • Re: Unable to decommission a Windows 2008 DC via dcpromo
      ... Can you open and compare sysvol and netlogon share on both DCs? ... Verifying that the local machine server2, ... The File Replication Service Event log test ... Latency information for 8 entries in the vector were ...
      (microsoft.public.windows.server.active_directory)