data synchronisation

Hi,

I'm working with two databases on to physicaly separated servers: #1
is on a local machine en I can only connect to #2 via an ADSL
connection.
I need to syncrhonise the data. This works fine via the wizard from
the Enterprise Manager. But I want to get this done via a script form
the Query Analyzer that I can run whenever I want to. Something like:

insert into srv1.database.dbo.table1
select * from srv2.database.dbo.table1

When I do this I get an error about "linked servers". That surprises
me, because I have no linked servers configured and yet the wizard
works fine?

Can anyone tell me how to accomplish this?

tav
Jan Willemsjhmwillems@.hotmail.com (Jan) wrote in message news:<240176c1.0404060206.4bfaaca3@.posting.google.com>...
> Hi,
> I'm working with two databases on to physicaly separated servers: #1
> is on a local machine en I can only connect to #2 via an ADSL
> connection.
> I need to syncrhonise the data. This works fine via the wizard from
> the Enterprise Manager. But I want to get this done via a script form
> the Query Analyzer that I can run whenever I want to. Something like:
> insert into srv1.database.dbo.table1
> select * from srv2.database.dbo.table1
> When I do this I get an error about "linked servers". That surprises
> me, because I have no linked servers configured and yet the wizard
> works fine?
> Can anyone tell me how to accomplish this?
> tav
> Jan Willems

The Import/Export Data wizard uses a separate connection to each
server, so linked servers are not involved. The INSERT statement above
does require the linked servers to exist, however.

So you could just create the linked servers you need, or if that's not
possible for some reason, then you can save a DTS package from the
wizard, and execute it in whatever way is most convenient:

http://www.sqldts.com/default.aspx?104

Simon

data import tool

I'm trying to find a way to import data from a local access database into a
remote sql server database where the databases are similar and of the same
product (but different versions) and different enough with constraints, keys,
columns, that I can't use the SQL Server Import and Export Wizard (with my
current knowledge of it) to map table columns without things like null value
errors and adding insert values to disparate columns while doing a bulk copy.
So what I'm looking for is a tool that is a combination of an sql insert
statement and the bulk copy import wizard found in the SQL Server Management
studio.
The differences between product versions require more flexibility than I can
currently find without doing everything programatically with ado.net.
Any advice regarding this data migration greatly appreciated - thanks.So far the easiest way I can think of is to pre-modify the access tables
before I do an import. This is working - however now I'm looking for a way
for the sql server manager interface to remember all the table imports and
mappings - can everything be saved somehow to some kind of configuration file
in SQL Server Management Studio?
"segue" wrote:
> I'm trying to find a way to import data from a local access database into a
> remote sql server database where the databases are similar and of the same
> product (but different versions) and different enough with constraints, keys,
> columns, that I can't use the SQL Server Import and Export Wizard (with my
> current knowledge of it) to map table columns without things like null value
> errors and adding insert values to disparate columns while doing a bulk copy.
> So what I'm looking for is a tool that is a combination of an sql insert
> statement and the bulk copy import wizard found in the SQL Server Management
> studio.
> The differences between product versions require more flexibility than I can
> currently find without doing everything programatically with ado.net.
> Any advice regarding this data migration greatly appreciated - thanks.|||You can always do it with ADO.NET. But it may be simpler to just import the
access data as is into a staging SQL Server table using the Import Wizard,
and then write T-SQL script to modify the data to your specs.
Linchi
"segue" wrote:
> So far the easiest way I can think of is to pre-modify the access tables
> before I do an import. This is working - however now I'm looking for a way
> for the sql server manager interface to remember all the table imports and
> mappings - can everything be saved somehow to some kind of configuration file
> in SQL Server Management Studio?
> "segue" wrote:
> >
> > I'm trying to find a way to import data from a local access database into a
> > remote sql server database where the databases are similar and of the same
> > product (but different versions) and different enough with constraints, keys,
> > columns, that I can't use the SQL Server Import and Export Wizard (with my
> > current knowledge of it) to map table columns without things like null value
> > errors and adding insert values to disparate columns while doing a bulk copy.
> >
> > So what I'm looking for is a tool that is a combination of an sql insert
> > statement and the bulk copy import wizard found in the SQL Server Management
> > studio.
> > The differences between product versions require more flexibility than I can
> > currently find without doing everything programatically with ado.net.
> >
> > Any advice regarding this data migration greatly appreciated - thanks.

data import tool

I'm trying to find a way to import data from a local access database into a
remote sql server database where the databases are similar and of the same
product (but different versions) and different enough with constraints, keys,
columns, that I can't use the SQL Server Import and Export Wizard (with my
current knowledge of it) to map table columns without things like null value
errors and adding insert values to disparate columns while doing a bulk copy.
So what I'm looking for is a tool that is a combination of an sql insert
statement and the bulk copy import wizard found in the SQL Server Management
studio.
The differences between product versions require more flexibility than I can
currently find without doing everything programatically with ado.net.
Any advice regarding this data migration greatly appreciated - thanks.
So far the easiest way I can think of is to pre-modify the access tables
before I do an import. This is working - however now I'm looking for a way
for the sql server manager interface to remember all the table imports and
mappings - can everything be saved somehow to some kind of configuration file
in SQL Server Management Studio?
"segue" wrote:

> I'm trying to find a way to import data from a local access database into a
> remote sql server database where the databases are similar and of the same
> product (but different versions) and different enough with constraints, keys,
> columns, that I can't use the SQL Server Import and Export Wizard (with my
> current knowledge of it) to map table columns without things like null value
> errors and adding insert values to disparate columns while doing a bulk copy.
> So what I'm looking for is a tool that is a combination of an sql insert
> statement and the bulk copy import wizard found in the SQL Server Management
> studio.
> The differences between product versions require more flexibility than I can
> currently find without doing everything programatically with ado.net.
> Any advice regarding this data migration greatly appreciated - thanks.
|||You can always do it with ADO.NET. But it may be simpler to just import the
access data as is into a staging SQL Server table using the Import Wizard,
and then write T-SQL script to modify the data to your specs.
Linchi
"segue" wrote:
[vbcol=seagreen]
> So far the easiest way I can think of is to pre-modify the access tables
> before I do an import. This is working - however now I'm looking for a way
> for the sql server manager interface to remember all the table imports and
> mappings - can everything be saved somehow to some kind of configuration file
> in SQL Server Management Studio?
> "segue" wrote:

data import task

Hello - suggestions greatly appreciated.
I'm trying to import data from similar tables between a local
access database and a network accessible sql server.
After using the Microsoft SQL Server Management Studio import wizard
I get the following error message on execute.
- Pre-execute (Error)
Messages
Error 0xc0202009: Data Flow Task: An OLE DB error has occurred. Error code:
0x80040E21.
An OLE DB record is available. Source: "Microsoft SQL Native Client"
Hresult: 0x80040E21 Description: "Multiple-step OLE DB operation generated
errors. Check each OLE DB status value, if available. No work was done.".
(SQL Server Import and Export Wizard)
Error 0xc0202025: Data Flow Task: Cannot create an OLE DB accessor. Verify
that the column metadata is valid.
(SQL Server Import and Export Wizard)
Error 0xc004701a: Data Flow Task: component "Destination - CustomerShipping"
(61) failed the pre-execute phase and returned error code 0xC0202025.
(SQL Server Import and Export Wizard)Hi
I can't say exactly what the issue is, but searching google for your error
80040E21 seems to be related most of the time to the data or datatypes. You
may want to save the import as a SSIS package or create a SSIS package from
scratch and then you would have more control over it.
"segue" wrote:
> Hello - suggestions greatly appreciated.
> I'm trying to import data from similar tables between a local
> access database and a network accessible sql server.
> After using the Microsoft SQL Server Management Studio import wizard
> I get the following error message on execute.
> - Pre-execute (Error)
> Messages
> Error 0xc0202009: Data Flow Task: An OLE DB error has occurred. Error code:
> 0x80040E21.
> An OLE DB record is available. Source: "Microsoft SQL Native Client"
> Hresult: 0x80040E21 Description: "Multiple-step OLE DB operation generated
> errors. Check each OLE DB status value, if available. No work was done.".
> (SQL Server Import and Export Wizard)
> Error 0xc0202025: Data Flow Task: Cannot create an OLE DB accessor. Verify
> that the column metadata is valid.
> (SQL Server Import and Export Wizard)
> Error 0xc004701a: Data Flow Task: component "Destination - CustomerShipping"
> (61) failed the pre-execute phase and returned error code 0xC0202025.
> (SQL Server Import and Export Wizard)
>|||Thanks for the response.
The problem after changing a few things has manifested into what seems to be
data type constraints.
Iâ've tried suggestions â' changing column values varchar(10) to varchar(MAX)
or whatever or running an sql delete or update at the old data to remove
nulls but Iâ'm still getting these null constraint errors even though a select
shows there are no null values in the old database.
If anything comes to mind regarding dealing with constraints - appreciated.
Thanks.
"John Bell" wrote:
> Hi
> I can't say exactly what the issue is, but searching google for your error
> 80040E21 seems to be related most of the time to the data or datatypes. You
> may want to save the import as a SSIS package or create a SSIS package from
> scratch and then you would have more control over it.
> "segue" wrote:
> > Hello - suggestions greatly appreciated.
> >
> > I'm trying to import data from similar tables between a local
> > access database and a network accessible sql server.
> >
> > After using the Microsoft SQL Server Management Studio import wizard
> > I get the following error message on execute.
> >
> > - Pre-execute (Error)
> > Messages
> > Error 0xc0202009: Data Flow Task: An OLE DB error has occurred. Error code:
> > 0x80040E21.
> > An OLE DB record is available. Source: "Microsoft SQL Native Client"
> > Hresult: 0x80040E21 Description: "Multiple-step OLE DB operation generated
> > errors. Check each OLE DB status value, if available. No work was done.".
> > (SQL Server Import and Export Wizard)
> >
> > Error 0xc0202025: Data Flow Task: Cannot create an OLE DB accessor. Verify
> > that the column metadata is valid.
> > (SQL Server Import and Export Wizard)
> >
> > Error 0xc004701a: Data Flow Task: component "Destination - CustomerShipping"
> > (61) failed the pre-execute phase and returned error code 0xC0202025.
> > (SQL Server Import and Export Wizard)
> >|||First verify that the SQL Agent Account has Full Permissions to the Access
database.
You can build a package as anybody, but it will be executed by the Agent.
Second, Build the package from the server it will be executed from.
At Pre-Execute the data has not become visible.
so the issue revolves around connection. Permissions or naming.
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:4BC6F16B-7941-4734-BD16-7FC4571D5417@.microsoft.com...
> Hi
> I can't say exactly what the issue is, but searching google for your error
> 80040E21 seems to be related most of the time to the data or datatypes.
> You
> may want to save the import as a SSIS package or create a SSIS package
> from
> scratch and then you would have more control over it.
> "segue" wrote:
>> Hello - suggestions greatly appreciated.
>> I'm trying to import data from similar tables between a local
>> access database and a network accessible sql server.
>> After using the Microsoft SQL Server Management Studio import wizard
>> I get the following error message on execute.
>> - Pre-execute (Error)
>> Messages
>> Error 0xc0202009: Data Flow Task: An OLE DB error has occurred. Error
>> code:
>> 0x80040E21.
>> An OLE DB record is available. Source: "Microsoft SQL Native Client"
>> Hresult: 0x80040E21 Description: "Multiple-step OLE DB operation
>> generated
>> errors. Check each OLE DB status value, if available. No work was done.".
>> (SQL Server Import and Export Wizard)
>> Error 0xc0202025: Data Flow Task: Cannot create an OLE DB accessor.
>> Verify
>> that the column metadata is valid.
>> (SQL Server Import and Export Wizard)
>> Error 0xc004701a: Data Flow Task: component "Destination -
>> CustomerShipping"
>> (61) failed the pre-execute phase and returned error code 0xC0202025.
>> (SQL Server Import and Export Wizard)|||Hi
If this was a spreadsheet I would guess there are blank cells at the end of
the range, but as access is the data source I am not sure why this occurs. I
am not sure if you have already created the destination table, but you need
to make the column nullable if you want it to be added. Have you pre-created
the destination table or does the package create it?
Also check out the topic "Handling Errors in Data" in Books online which
will allow you to move any rows that are not inserted into the database
elsewhere so you can see what they are.
John
"segue" wrote:
> Thanks for the response.
> The problem after changing a few things has manifested into what seems to be
> data type constraints.
> Iâ've tried suggestions â' changing column values varchar(10) to varchar(MAX)
> or whatever or running an sql delete or update at the old data to remove
> nulls but Iâ'm still getting these null constraint errors even though a select
> shows there are no null values in the old database.
> If anything comes to mind regarding dealing with constraints - appreciated.
> Thanks.
>
> "John Bell" wrote:
> > Hi
> >
> > I can't say exactly what the issue is, but searching google for your error
> > 80040E21 seems to be related most of the time to the data or datatypes. You
> > may want to save the import as a SSIS package or create a SSIS package from
> > scratch and then you would have more control over it.
> >
> > "segue" wrote:
> >
> > > Hello - suggestions greatly appreciated.
> > >
> > > I'm trying to import data from similar tables between a local
> > > access database and a network accessible sql server.
> > >
> > > After using the Microsoft SQL Server Management Studio import wizard
> > > I get the following error message on execute.
> > >
> > > - Pre-execute (Error)
> > > Messages
> > > Error 0xc0202009: Data Flow Task: An OLE DB error has occurred. Error code:
> > > 0x80040E21.
> > > An OLE DB record is available. Source: "Microsoft SQL Native Client"
> > > Hresult: 0x80040E21 Description: "Multiple-step OLE DB operation generated
> > > errors. Check each OLE DB status value, if available. No work was done.".
> > > (SQL Server Import and Export Wizard)
> > >
> > > Error 0xc0202025: Data Flow Task: Cannot create an OLE DB accessor. Verify
> > > that the column metadata is valid.
> > > (SQL Server Import and Export Wizard)
> > >
> > > Error 0xc004701a: Data Flow Task: component "Destination - CustomerShipping"
> > > (61) failed the pre-execute phase and returned error code 0xC0202025.
> > > (SQL Server Import and Export Wizard)
> > >|||In the select convert the columns to isnull([Column],'ISNULL') for strings
Then after the import you should be able to better locate them.
But if the select is failing to return records becuase views with join
columns haveing nulls.
then you will have to fix the underlying views.
-Randy Pitkin
-Information Systems Consultant since 1983
"segue" <segue@.discussions.microsoft.com> wrote in message
news:34CC113F-B137-4EB9-A6C7-507D733B0088@.microsoft.com...
> Thanks for the response.
> The problem after changing a few things has manifested into what seems to
> be
> data type constraints.
> I've tried suggestions - changing column values varchar(10) to
> varchar(MAX)
> or whatever or running an sql delete or update at the old data to remove
> nulls but I'm still getting these null constraint errors even though a
> select
> shows there are no null values in the old database.
> If anything comes to mind regarding dealing with constraints -
> appreciated.
> Thanks.
>
> "John Bell" wrote:
>> Hi
>> I can't say exactly what the issue is, but searching google for your
>> error
>> 80040E21 seems to be related most of the time to the data or datatypes.
>> You
>> may want to save the import as a SSIS package or create a SSIS package
>> from
>> scratch and then you would have more control over it.
>> "segue" wrote:
>> > Hello - suggestions greatly appreciated.
>> >
>> > I'm trying to import data from similar tables between a local
>> > access database and a network accessible sql server.
>> >
>> > After using the Microsoft SQL Server Management Studio import wizard
>> > I get the following error message on execute.
>> >
>> > - Pre-execute (Error)
>> > Messages
>> > Error 0xc0202009: Data Flow Task: An OLE DB error has occurred. Error
>> > code:
>> > 0x80040E21.
>> > An OLE DB record is available. Source: "Microsoft SQL Native Client"
>> > Hresult: 0x80040E21 Description: "Multiple-step OLE DB operation
>> > generated
>> > errors. Check each OLE DB status value, if available. No work was
>> > done.".
>> > (SQL Server Import and Export Wizard)
>> >
>> > Error 0xc0202025: Data Flow Task: Cannot create an OLE DB accessor.
>> > Verify
>> > that the column metadata is valid.
>> > (SQL Server Import and Export Wizard)
>> >
>> > Error 0xc004701a: Data Flow Task: component "Destination -
>> > CustomerShipping"
>> > (61) failed the pre-execute phase and returned error code 0xC0202025.
>> > (SQL Server Import and Export Wizard)
>> >|||Thanks for the great ideas. I'm building (through the wizard?) the
"package"?
I'm not sure what "package" means exactly (in what context).
As far as permissions go the access is local to my computer and the sql is
remote. I'm not using an account to the access db which doesn't seem
necessary and I am using an account naturally for the SQL server and
connection. I'm able to perform ado.net w/asp.net and sql queries with the
same account
Any tasks to disect what's below greatly appreciated.
At Pre-Execute the data has not become visible so the issue revolves around
connection, permissions or naming.
Regards
"Randy Pitkin" wrote:
> First verify that the SQL Agent Account has Full Permissions to the Access
> database.
> You can build a package as anybody, but it will be executed by the Agent.
> Second, Build the package from the server it will be executed from.
> At Pre-Execute the data has not become visible.
> so the issue revolves around connection. Permissions or naming.
>
>
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:4BC6F16B-7941-4734-BD16-7FC4571D5417@.microsoft.com...
> > Hi
> >
> > I can't say exactly what the issue is, but searching google for your error
> > 80040E21 seems to be related most of the time to the data or datatypes.
> > You
> > may want to save the import as a SSIS package or create a SSIS package
> > from
> > scratch and then you would have more control over it.
> >
> > "segue" wrote:
> >
> >> Hello - suggestions greatly appreciated.
> >>
> >> I'm trying to import data from similar tables between a local
> >> access database and a network accessible sql server.
> >>
> >> After using the Microsoft SQL Server Management Studio import wizard
> >> I get the following error message on execute.
> >>
> >> - Pre-execute (Error)
> >> Messages
> >> Error 0xc0202009: Data Flow Task: An OLE DB error has occurred. Error
> >> code:
> >> 0x80040E21.
> >> An OLE DB record is available. Source: "Microsoft SQL Native Client"
> >> Hresult: 0x80040E21 Description: "Multiple-step OLE DB operation
> >> generated
> >> errors. Check each OLE DB status value, if available. No work was done.".
> >> (SQL Server Import and Export Wizard)
> >>
> >> Error 0xc0202025: Data Flow Task: Cannot create an OLE DB accessor.
> >> Verify
> >> that the column metadata is valid.
> >> (SQL Server Import and Export Wizard)
> >>
> >> Error 0xc004701a: Data Flow Task: component "Destination -
> >> CustomerShipping"
> >> (61) failed the pre-execute phase and returned error code 0xC0202025.
> >> (SQL Server Import and Export Wizard)
> >>
>
>|||The table is already created and the table's database is a 3rd party .NET
based app., so I'm trying to import into a table that already exists.
The columns for that table have keys that are not nullable of course. The
error messages haven't mentioned those columns. The columns that are
mentioned in the null value error messages I've tried adding values for to
that access table with no luck.
I can't change the columns I'm importing to other than value types and sizes
when I bring up their design view in VS2005.
Suggestions greatly appreciated - thanks.
"John Bell" wrote:
> Hi
> If this was a spreadsheet I would guess there are blank cells at the end of
> the range, but as access is the data source I am not sure why this occurs. I
> am not sure if you have already created the destination table, but you need
> to make the column nullable if you want it to be added. Have you pre-created
> the destination table or does the package create it?
> Also check out the topic "Handling Errors in Data" in Books online which
> will allow you to move any rows that are not inserted into the database
> elsewhere so you can see what they are.
> John
> "segue" wrote:
> >
> > Thanks for the response.
> >
> > The problem after changing a few things has manifested into what seems to be
> > data type constraints.
> >
> > Iâ've tried suggestions â' changing column values varchar(10) to varchar(MAX)
> > or whatever or running an sql delete or update at the old data to remove
> > nulls but Iâ'm still getting these null constraint errors even though a select
> > shows there are no null values in the old database.
> >
> > If anything comes to mind regarding dealing with constraints - appreciated.
> >
> > Thanks.
> >
> >
> > "John Bell" wrote:
> >
> > > Hi
> > >
> > > I can't say exactly what the issue is, but searching google for your error
> > > 80040E21 seems to be related most of the time to the data or datatypes. You
> > > may want to save the import as a SSIS package or create a SSIS package from
> > > scratch and then you would have more control over it.
> > >
> > > "segue" wrote:
> > >
> > > > Hello - suggestions greatly appreciated.
> > > >
> > > > I'm trying to import data from similar tables between a local
> > > > access database and a network accessible sql server.
> > > >
> > > > After using the Microsoft SQL Server Management Studio import wizard
> > > > I get the following error message on execute.
> > > >
> > > > - Pre-execute (Error)
> > > > Messages
> > > > Error 0xc0202009: Data Flow Task: An OLE DB error has occurred. Error code:
> > > > 0x80040E21.
> > > > An OLE DB record is available. Source: "Microsoft SQL Native Client"
> > > > Hresult: 0x80040E21 Description: "Multiple-step OLE DB operation generated
> > > > errors. Check each OLE DB status value, if available. No work was done.".
> > > > (SQL Server Import and Export Wizard)
> > > >
> > > > Error 0xc0202025: Data Flow Task: Cannot create an OLE DB accessor. Verify
> > > > that the column metadata is valid.
> > > > (SQL Server Import and Export Wizard)
> > > >
> > > > Error 0xc004701a: Data Flow Task: component "Destination - CustomerShipping"
> > > > (61) failed the pre-execute phase and returned error code 0xC0202025.
> > > > (SQL Server Import and Export Wizard)
> > > >|||Hi
Randy has given an option to overcome the potential nullability of the
columns, another would be to change the table you load into and allow null
columns etc and then you can view the data and sort it out or make the
process a two stage process permanently and rectify the data as you import it.
John
"segue" wrote:
> The table is already created and the table's database is a 3rd party .NET
> based app., so I'm trying to import into a table that already exists.
> The columns for that table have keys that are not nullable of course. The
> error messages haven't mentioned those columns. The columns that are
> mentioned in the null value error messages I've tried adding values for to
> that access table with no luck.
> I can't change the columns I'm importing to other than value types and sizes
> when I bring up their design view in VS2005.
> Suggestions greatly appreciated - thanks.
>
> "John Bell" wrote:
> > Hi
> >
> > If this was a spreadsheet I would guess there are blank cells at the end of
> > the range, but as access is the data source I am not sure why this occurs. I
> > am not sure if you have already created the destination table, but you need
> > to make the column nullable if you want it to be added. Have you pre-created
> > the destination table or does the package create it?
> >
> > Also check out the topic "Handling Errors in Data" in Books online which
> > will allow you to move any rows that are not inserted into the database
> > elsewhere so you can see what they are.
> >
> > John
> >
> > "segue" wrote:
> >
> > >
> > > Thanks for the response.
> > >
> > > The problem after changing a few things has manifested into what seems to be
> > > data type constraints.
> > >
> > > Iâ've tried suggestions â' changing column values varchar(10) to varchar(MAX)
> > > or whatever or running an sql delete or update at the old data to remove
> > > nulls but Iâ'm still getting these null constraint errors even though a select
> > > shows there are no null values in the old database.
> > >
> > > If anything comes to mind regarding dealing with constraints - appreciated.
> > >
> > > Thanks.
> > >
> > >
> > > "John Bell" wrote:
> > >
> > > > Hi
> > > >
> > > > I can't say exactly what the issue is, but searching google for your error
> > > > 80040E21 seems to be related most of the time to the data or datatypes. You
> > > > may want to save the import as a SSIS package or create a SSIS package from
> > > > scratch and then you would have more control over it.
> > > >
> > > > "segue" wrote:
> > > >
> > > > > Hello - suggestions greatly appreciated.
> > > > >
> > > > > I'm trying to import data from similar tables between a local
> > > > > access database and a network accessible sql server.
> > > > >
> > > > > After using the Microsoft SQL Server Management Studio import wizard
> > > > > I get the following error message on execute.
> > > > >
> > > > > - Pre-execute (Error)
> > > > > Messages
> > > > > Error 0xc0202009: Data Flow Task: An OLE DB error has occurred. Error code:
> > > > > 0x80040E21.
> > > > > An OLE DB record is available. Source: "Microsoft SQL Native Client"
> > > > > Hresult: 0x80040E21 Description: "Multiple-step OLE DB operation generated
> > > > > errors. Check each OLE DB status value, if available. No work was done.".
> > > > > (SQL Server Import and Export Wizard)
> > > > >
> > > > > Error 0xc0202025: Data Flow Task: Cannot create an OLE DB accessor. Verify
> > > > > that the column metadata is valid.
> > > > > (SQL Server Import and Export Wizard)
> > > > >
> > > > > Error 0xc004701a: Data Flow Task: component "Destination - CustomerShipping"
> > > > > (61) failed the pre-execute phase and returned error code 0xC0202025.
> > > > > (SQL Server Import and Export Wizard)
> > > > >