JWColby
jwcolby at colbyconsulting.com
Mon Jan 22 13:34:58 CST 2007
I just ran an update query. I built an insert query of one table, an insert query of the other, cut and pasted to make one, then ran it. Both tables are on one physical machine, but different physical databases (different database files). John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Robert L. Stewart Sent: Monday, January 22, 2007 2:20 PM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Migrating tables to a new database Depending on how you did it, that is not bad. I think that using SSIS would have given you better performance. and, it is the replacement for DTS. At 12:00 PM 1/22/2007, you wrote: >Date: Mon, 22 Jan 2007 11:17:39 -0500 >From: "JWColby" <jwcolby at colbyconsulting.com> >Subject: Re: [dba-SQLServer] Migrating tables to a new database >To: <dba-sqlserver at databaseadvisors.com> >Message-ID: <004a01c73e40$d69f9480$657aa8c0 at m6805> >Content-Type: text/plain; charset="us-ascii" > >Just an FYI. It took two hours two minutes to copy 53 million records >consisting of the just the PK, Fname, Mname and Lname from one table in >one database to a table in another database - with indexes on only an >integer FK, a currently empty MatchCode field and an autoincrement PK >being created as well. > >I do not have any experience to tell me whether this is fast, slow or >indifferent > >The system is a dual core AMD X64 2.8 ghz processor with 3 gb ram and a >1 tbyte raid 6 volume, running on Windows2003. > > >John W. Colby >Colby Consulting >www.ColbyConsulting.com _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com