#DateForumTypeThreadPost
801 Apr 2016 @ 12:10 PDTDatabaseReplyCopy data from one database to another on the same server Copy time seems to have doubled, as we have been observing it for almost few months now. The only thing i know is new server include compression but the earlier one was not.     ...
717 Mar 2016 @ 10:41 PDTDatabaseReplyCopy data from one database to another on the same server I meant that DB servers were changed from one server configuration to another.
614 Mar 2016 @ 09:35 PDTDatabaseReplyCopy data from one database to another on the same server Thanks Dieter.  Currently we do follow the 1st approach you mentioned. This approach was working fine until we moved to a different infrastructure where the copy time doubled. Are there any ...
512 Mar 2016 @ 08:53 PSTDatabaseReplyCopy data from one database to another on the same server Thanks Todd. We tried the same but couldn't see much difference in copy times. As per my understanding on the approach you said is below. begin tran; del from tbl; end tran;   begin ...
424 Nov 2015 @ 11:43 PSTDatabaseReplyCopy data from one database to another on the same server adding some addnl info.. the purpose is to isolate two process working on the datasets, where one process just stops to allow copy and then takes over updating/inserting data to the source. T...
324 Nov 2015 @ 11:28 PSTDatabaseTopicCopy data from one database to another on the same server using del from tbl; insert select from tbl;  for copy data from one DB region to another take a lot of time.(same DB server) copy is done just between two mirror databases. Is there any...
231 Aug 2015 @ 11:30 PDTDatabaseReplyTIMESTAMP values gets updated with UTC values via Stored procedure.Thanks Fred . The SP seems to have been recompiled with UTC. We re-compiled again with "AT local" using ALTER and it worked as expected.
125 Aug 2015 @ 02:15 PDTDatabaseTopicTIMESTAMP values gets updated with UTC values via Stored procedure.We have the column defined as below beg_ts TIMESTAMP(6) WITH TIME ZONE. The column when updated via BTEQ, MACRO gives the output as below 8/21/2015 23:22:55.320000-07:00 (at local timezone) whe...