September 29, 2010 at 5:42 am
I have 25 sql7 server where data is updated within 15 minutes . I need to transfer data from that to a centralised sql 2005 server at a regular interval of 115 minutes. I am new to sql server 2005 kindly suggest best way to transfer data and steps to transfer data.
September 29, 2010 at 7:56 am
What have you looked at so far? What options have you considered?
For best practices on asking questions, please read the following article: Forum Etiquette: How to post data/code on a forum to get the best help[/url]
September 29, 2010 at 10:16 am
I have heard of ssis packages but how to conditionally pull data and delete after confirming data has been inserted in centralised server.
September 29, 2010 at 12:06 pm
the.hank (9/29/2010)
I have heard of ssis packages but how to conditionally pull data and delete after confirming data has been inserted in centralised server.
In other words, you're trying to use SSIS without taking the time to learn how to do it, and you're expecting us to do part of that work for you?
For best practices on asking questions, please read the following article: Forum Etiquette: How to post data/code on a forum to get the best help[/url]
September 29, 2010 at 11:07 pm
If u have read my previous message i had asked to suggest best way to solve the problem ..GOT the word meaning "SUGGEST" not do my work ..i know how to do the work.....if u can't help pls don't make useless comments...
September 30, 2010 at 7:25 am
the.hank (9/29/2010)
If u have read my previous message i had asked to suggest best way to solve the problem ..GOT the word meaning "SUGGEST" not do my work ..i know how to do the work.....if u can't help pls don't make useless comments...
I apologize if I made an incorrect assumption about you, but when I asked:
Alvin Ramard (9/29/2010)
What have you looked at so far? What options have you considered?
You responded with:
the.hank (9/29/2010)
I have heard of ssis packages but how to conditionally pull data and delete after confirming data has been inserted in centralised server.
First, you did not answer my question.
Second, to me, that answers tells me that you have not taken the time to learn about SSIS and that you are about to undertake a project that is way beyond your level of knowledge. Come back with a post that indicates that you at least know something about copying data with SSIS and you'll see that you'll get better replies.
People that can demonstrate that they have put effort into solving their own problems will generally get better help than those that come in here asking for help without demonstrating any effort.
For best practices on asking questions, please read the following article: Forum Etiquette: How to post data/code on a forum to get the best help[/url]
October 3, 2010 at 4:29 am
I have been able to create a ssis package to transfer data from one server to another by scheduling a job and deleting the data under the job itself. So should i try to make 25 seperate jobs to transfer data. Is there any other way.?
October 3, 2010 at 5:08 am
Is the requirement exactly the same for each server?
Is the schema exactly the same for each server?
If so, you can execute the same process over and over again, against the different servers. You'll need to make use of a FOREACH loop, expressions to control your connection to the different servers and something for your FOREACH loop to use for enumeration (a recordset or array of connection info).
If the answer to either of the first two questions is no, it is likely that you'll need separate data flows, or some fancy control-flow logic.
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
October 4, 2010 at 10:24 am
Also, as a follow up to what Phil had to say, I would not create 25 jobs, or whatever the number ends up being, if the extractions always take place together. In that case, I would only create on job to execute 1 package. That SSIS package would contain the logic for all the extractions. That package could contain all the extraction logic, or it could call the other packages, each one doing a separate extraction. Both options are acceptable. Which option you pick depends on your rules/standards for how much you allow in one package.
The logic for deleting the records probably should be taken out of the job and brought into the SSIS package. I would execute the deletion after successful execution of the extraction.
For best practices on asking questions, please read the following article: Forum Etiquette: How to post data/code on a forum to get the best help[/url]
October 11, 2010 at 12:10 am
Thank u all for ur suggestions. I have made a single ssis package and a single job and been able to tranfer data.
October 11, 2010 at 12:44 am
the.hank (10/11/2010)
Thank u all for ur suggestions. I have made a single ssis package and a single job and been able to tranfer data.
Bravo! 😎
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
October 11, 2010 at 7:30 am
Phil Parkin (10/11/2010)
the.hank (10/11/2010)
Thank u all for ur suggestions. I have made a single ssis package and a single job and been able to tranfer data.Bravo! 😎
Well Done! 🙂
For best practices on asking questions, please read the following article: Forum Etiquette: How to post data/code on a forum to get the best help[/url]
Viewing 12 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply