XPost: microsoft.public.sqlserver.programming   
   From: genew@ocis.net   
      
   On Wed, 02 May 2012 23:41:10 +0200, Erland Sommarskog   
    wrote:   
      
   >Gene Wirchenko (genew@ocis.net) writes:   
   >>      No, it does not.  I am the developer.  My system has the   
   >> development database.  The other system is elsewhere and will   
   >> eventually be the production system.   
   >   
   >The the proper way is to keep code under version control and install   
   >from scripts. Copying a full database is only going to work for V1.0   
   >anyway.   
      
        When I change table structures, I use scripting, and I am fine   
   with that then.   
      
        I want to be able to slurp the whole database so that I will be   
   able to get a copy of the production data for debugging use.  On the   
   current system, when there are problems, my boss may send a copy of   
   the database with instructions to look at certain rows.  This makes it   
   much easier to replicate trouble, and is not very difficult for him to   
   do.   
      
        So what is the best way of doing this?  I am getting conflicting   
   data.   
      
   Sincerely,   
      
   Gene Wirchenko   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)