Showing posts with label transfer. Show all posts
Showing posts with label transfer. Show all posts

Thursday, March 22, 2012

Bug? Transfer SQL Server Objects Task - error when copying Views

I'm trying to copy data over using a Transfer SQL Server Objects Task however I get problems trying to copy over views. I get the similar error (pre sp1) when using import/export wizard and copying over views. Now with SP1 the views just don't transfer. I'm transferring from SQL 2005 to SQL 2005. The error I get is:

Error: 0xC002F363 at Transfer Data (NEW), Transfer SQL Server Objects Task: Table "vw_XXXX" does not exist at the source. Task failed: Transfer Data (NEW)

I know the view exists at the source because:

A) I can select it in the Views List Collection within the Transfer SQL Server Objects Task
B) I'm using the view on the source

Somehow the views are not transferring. Anyone have any ideas?

I just noticed that SP1 import/export wizard copies the views to the destination as tables!!! What is going on here?!?! Is this why I'm having problems in the Transfer SQL Server Objects Task as stated above?|||Also get Error: 0x80004005 on Microsoft SQL Native Client when using this Task about 30% of the time.|||If you do a search you will find that the Transfer Objects Task is pretty buggy. I would avoid it until those issues are resolved.|||

So has this been fixed? I'm getting the same error:

[Transfer SQL Server Objects Task] Error: Table "tbl_BOL_ShipID" does not exist at the source.

I know the referenced table exists at the source.

|||Do you have the CopySchema option set to true? This is a frequent source of these error messages.|||

I've use the same way.

This Task checks the Objects and Columns casesensitive.

So all Objects and Columns must be identically named.

|||I believe some work was done on the case sensitivity issue in SP2. Are you still seeing this problem after upgrading?sql

Bug? Transfer SQL Server Objects Task - error when copying Views

I'm trying to copy data over using a Transfer SQL Server Objects Task however I get problems trying to copy over views. I get the similar error (pre sp1) when using import/export wizard and copying over views. Now with SP1 the views just don't transfer. I'm transferring from SQL 2005 to SQL 2005. The error I get is:

Error: 0xC002F363 at Transfer Data (NEW), Transfer SQL Server Objects Task: Table "vw_XXXX" does not exist at the source. Task failed: Transfer Data (NEW)

I know the view exists at the source because:

A) I can select it in the Views List Collection within the Transfer SQL Server Objects Task
B) I'm using the view on the source

Somehow the views are not transferring. Anyone have any ideas?

I just noticed that SP1 import/export wizard copies the views to the destination as tables!!! What is going on here?!?! Is this why I'm having problems in the Transfer SQL Server Objects Task as stated above?|||Also get Error: 0x80004005 on Microsoft SQL Native Client when using this Task about 30% of the time.|||If you do a search you will find that the Transfer Objects Task is pretty buggy. I would avoid it until those issues are resolved.|||

So has this been fixed? I'm getting the same error:

[Transfer SQL Server Objects Task] Error: Table "tbl_BOL_ShipID" does not exist at the source.

I know the referenced table exists at the source.

|||Do you have the CopySchema option set to true? This is a frequent source of these error messages.|||

I've use the same way.

This Task checks the Objects and Columns casesensitive.

So all Objects and Columns must be identically named.

|||I believe some work was done on the case sensitivity issue in SP2. Are you still seeing this problem after upgrading?

Bug? Transfer SQL Server Objects Task - error when copying Views

I'm trying to copy data over using a Transfer SQL Server Objects Task however I get problems trying to copy over views. I get the similar error (pre sp1) when using import/export wizard and copying over views. Now with SP1 the views just don't transfer. I'm transferring from SQL 2005 to SQL 2005. The error I get is:

Error: 0xC002F363 at Transfer Data (NEW), Transfer SQL Server Objects Task: Table "vw_XXXX" does not exist at the source. Task failed: Transfer Data (NEW)

I know the view exists at the source because:

A) I can select it in the Views List Collection within the Transfer SQL Server Objects Task
B) I'm using the view on the source

Somehow the views are not transferring. Anyone have any ideas?

I just noticed that SP1 import/export wizard copies the views to the destination as tables!!! What is going on here?!?! Is this why I'm having problems in the Transfer SQL Server Objects Task as stated above?|||Also get Error: 0x80004005 on Microsoft SQL Native Client when using this Task about 30% of the time.|||If you do a search you will find that the Transfer Objects Task is pretty buggy. I would avoid it until those issues are resolved.|||

So has this been fixed? I'm getting the same error:

[Transfer SQL Server Objects Task] Error: Table "tbl_BOL_ShipID" does not exist at the source.

I know the referenced table exists at the source.

|||Do you have the CopySchema option set to true? This is a frequent source of these error messages.|||

I've use the same way.

This Task checks the Objects and Columns casesensitive.

So all Objects and Columns must be identically named.

|||I believe some work was done on the case sensitivity issue in SP2. Are you still seeing this problem after upgrading?

Bug? Transfer SQL Server Objects Task - error when copying Views

I'm trying to copy data over using a Transfer SQL Server Objects Task however I get problems trying to copy over views. I get the similar error (pre sp1) when using import/export wizard and copying over views. Now with SP1 the views just don't transfer. I'm transferring from SQL 2005 to SQL 2005. The error I get is:

Error: 0xC002F363 at Transfer Data (NEW), Transfer SQL Server Objects Task: Table "vw_XXXX" does not exist at the source. Task failed: Transfer Data (NEW)

I know the view exists at the source because:

A) I can select it in the Views List Collection within the Transfer SQL Server Objects Task
B) I'm using the view on the source

Somehow the views are not transferring. Anyone have any ideas?

I just noticed that SP1 import/export wizard copies the views to the destination as tables!!! What is going on here?!?! Is this why I'm having problems in the Transfer SQL Server Objects Task as stated above?|||Also get Error: 0x80004005 on Microsoft SQL Native Client when using this Task about 30% of the time.|||If you do a search you will find that the Transfer Objects Task is pretty buggy. I would avoid it until those issues are resolved.|||

So has this been fixed? I'm getting the same error:

[Transfer SQL Server Objects Task] Error: Table "tbl_BOL_ShipID" does not exist at the source.

I know the referenced table exists at the source.

|||Do you have the CopySchema option set to true? This is a frequent source of these error messages.|||

I've use the same way.

This Task checks the Objects and Columns casesensitive.

So all Objects and Columns must be identically named.

|||I believe some work was done on the case sensitivity issue in SP2. Are you still seeing this problem after upgrading?

Thursday, March 8, 2012

Bug in MSKB918992 ("How to transfer the logins...") - How to report?

Hi all,
I found a bug in the listing in Knowledge Base Article 918992 ("How to
transfer the logins and the passwords between instances of SQL Server
2005"). Instead of
SET @.tmpstr = 'CREATE LOGIN ' + QUOTENAME( @.name ) + ' WITH PASSWORD = ' +
@.PWD_string + ' HASHED, SID = ' + @.SID_string + ' DEFAULT_DATABASE = ['
+
@.defaultdb + ']'
it should be
SET @.tmpstr = 'CREATE LOGIN ' + QUOTENAME( @.name ) + ' WITH PASSWORD = ' +
@.PWD_string + ' HASHED, SID = ' + @.SID_string + ', DEFAULT_DATABASE = ['
+
@.defaultdb + ']'
A colon has to be added before DEFAULT_DATABASE. Now while this little bit
of information might be useful to somebody here, the primary reason for this
posting is that the stupid interface for reporting bugs on the MS web site
(http://connect.microsoft.com/feedba...aspx?SiteID=68) drove me
nuts! It wouldn't let me sign in for reporting bugs, I could only search. Is
this offering restricted to a selection of VIP users or something? Can
anybody enlighten me here? I was just trying to be helpful...
Thanks and best regards
Nils LoeberBy VIPs perhaps you meant MVPs, and yes, they can report bugs via that site.
However, you should be able to also, and so should I. I got stuck in the
loop where you keep getting back to the page telling you that you need to
sign in to submit feedback. I've pinged a member of the dev team to find out
if they really meant for everybody to send email to the administrator
account listed on https://connect.microsoft.com/SQLServer. At the moment,
that would appear to be the only option to get access but I don't think it's
meant to be gated like that.
In the meantime, however, at the bottom of every KB article on the support
site is a section that allows you to submit comments/bugs. Scroll to the
bottom of http://support.microsoft.com/kb/918992/en-us and have a look. The
support folks will be reading that information and can correct the article
directly.
Sincerely,
Stephen Dybing
This posting is provided "AS IS" with no warranties, and confers no rights.
"Nils Loeber" <nils@.NOSPAMFORMEPLEASEnils-loeber.de> wrote in message
news:u1eXq%23xiGHA.5036@.TK2MSFTNGP04.phx.gbl...
> Hi all,
> I found a bug in the listing in Knowledge Base Article 918992 ("How to
> transfer the logins and the passwords between instances of SQL Server
> 2005"). Instead of
> SET @.tmpstr = 'CREATE LOGIN ' + QUOTENAME( @.name ) + ' WITH PASSWORD = ' +
> @.PWD_string + ' HASHED, SID = ' + @.SID_string + ' DEFAULT_DATABASE = [
' +
> @.defaultdb + ']'
> it should be
> SET @.tmpstr = 'CREATE LOGIN ' + QUOTENAME( @.name ) + ' WITH PASSWORD = ' +
> @.PWD_string + ' HASHED, SID = ' + @.SID_string + ', DEFAULT_DATABASE = [
;' +
> @.defaultdb + ']'
> A colon has to be added before DEFAULT_DATABASE. Now while this little bit
> of information might be useful to somebody here, the primary reason for
> this posting is that the stupid interface for reporting bugs on the MS web
> site (http://connect.microsoft.com/feedba...aspx?SiteID=68) drove
> me nuts! It wouldn't let me sign in for reporting bugs, I could only
> search. Is this offering restricted to a selection of VIP users or
> something? Can anybody enlighten me here? I was just trying to be
> helpful...
> Thanks and best regards
> Nils Loeber
>|||OK, the text has been cleaned up a little bit in the attempt to make it
clear that you have to search for the issue before you can submit new
feedback. This is done in the attempt to cut down on duplicates. Try the
search to find out if it's already been reported and if not, if you have the
ability to submit a new issue. I'll point out that it's not allowing me to
yet, they're working on it...
Sincerely,
Stephen Dybing
This posting is provided "AS IS" with no warranties, and confers no rights.
"Steve Dybing [MSFT]" <steve.dybing@.online.microsoft.com> wrote in messa
ge
news:uR%23M$SkjGHA.4884@.TK2MSFTNGP03.phx.gbl...
> By VIPs perhaps you meant MVPs, and yes, they can report bugs via that
> site. However, you should be able to also, and so should I. I got stuck in
> the loop where you keep getting back to the page telling you that you need
> to sign in to submit feedback. I've pinged a member of the dev team to
> find out if they really meant for everybody to send email to the
> administrator account listed on https://connect.microsoft.com/SQLServer.
> At the moment, that would appear to be the only option to get access but I
> don't think it's meant to be gated like that.
> In the meantime, however, at the bottom of every KB article on the support
> site is a section that allows you to submit comments/bugs. Scroll to the
> bottom of http://support.microsoft.com/kb/918992/en-us and have a look.
> The support folks will be reading that information and can correct the
> article directly.
> --
> Sincerely,
> Stephen Dybing
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> "Nils Loeber" <nils@.NOSPAMFORMEPLEASEnils-loeber.de> wrote in message
> news:u1eXq%23xiGHA.5036@.TK2MSFTNGP04.phx.gbl...
>|||By VIPs perhaps you meant MVPs, and yes, they can report bugs via that site.
However, you should be able to also, and so should I. I got stuck in the
loop where you keep getting back to the page telling you that you need to
sign in to submit feedback. I've pinged a member of the dev team to find out
if they really meant for everybody to send email to the administrator
account listed on https://connect.microsoft.com/SQLServer. At the moment,
that would appear to be the only option to get access but I don't think it's
meant to be gated like that.
In the meantime, however, at the bottom of every KB article on the support
site is a section that allows you to submit comments/bugs. Scroll to the
bottom of http://support.microsoft.com/kb/918992/en-us and have a look. The
support folks will be reading that information and can correct the article
directly.
Sincerely,
Stephen Dybing
This posting is provided "AS IS" with no warranties, and confers no rights.
"Nils Loeber" <nils@.NOSPAMFORMEPLEASEnils-loeber.de> wrote in message
news:u1eXq%23xiGHA.5036@.TK2MSFTNGP04.phx.gbl...
> Hi all,
> I found a bug in the listing in Knowledge Base Article 918992 ("How to
> transfer the logins and the passwords between instances of SQL Server
> 2005"). Instead of
> SET @.tmpstr = 'CREATE LOGIN ' + QUOTENAME( @.name ) + ' WITH PASSWORD = ' +
> @.PWD_string + ' HASHED, SID = ' + @.SID_string + ' DEFAULT_DATABASE = [
' +
> @.defaultdb + ']'
> it should be
> SET @.tmpstr = 'CREATE LOGIN ' + QUOTENAME( @.name ) + ' WITH PASSWORD = ' +
> @.PWD_string + ' HASHED, SID = ' + @.SID_string + ', DEFAULT_DATABASE = [
;' +
> @.defaultdb + ']'
> A colon has to be added before DEFAULT_DATABASE. Now while this little bit
> of information might be useful to somebody here, the primary reason for
> this posting is that the stupid interface for reporting bugs on the MS web
> site (http://connect.microsoft.com/feedba...aspx?SiteID=68) drove
> me nuts! It wouldn't let me sign in for reporting bugs, I could only
> search. Is this offering restricted to a selection of VIP users or
> something? Can anybody enlighten me here? I was just trying to be
> helpful...
> Thanks and best regards
> Nils Loeber
>|||OK, the text has been cleaned up a little bit in the attempt to make it
clear that you have to search for the issue before you can submit new
feedback. This is done in the attempt to cut down on duplicates. Try the
search to find out if it's already been reported and if not, if you have the
ability to submit a new issue. I'll point out that it's not allowing me to
yet, they're working on it...
Sincerely,
Stephen Dybing
This posting is provided "AS IS" with no warranties, and confers no rights.
"Steve Dybing [MSFT]" <steve.dybing@.online.microsoft.com> wrote in messa
ge
news:uR%23M$SkjGHA.4884@.TK2MSFTNGP03.phx.gbl...
> By VIPs perhaps you meant MVPs, and yes, they can report bugs via that
> site. However, you should be able to also, and so should I. I got stuck in
> the loop where you keep getting back to the page telling you that you need
> to sign in to submit feedback. I've pinged a member of the dev team to
> find out if they really meant for everybody to send email to the
> administrator account listed on https://connect.microsoft.com/SQLServer.
> At the moment, that would appear to be the only option to get access but I
> don't think it's meant to be gated like that.
> In the meantime, however, at the bottom of every KB article on the support
> site is a section that allows you to submit comments/bugs. Scroll to the
> bottom of http://support.microsoft.com/kb/918992/en-us and have a look.
> The support folks will be reading that information and can correct the
> article directly.
> --
> Sincerely,
> Stephen Dybing
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> "Nils Loeber" <nils@.NOSPAMFORMEPLEASEnils-loeber.de> wrote in message
> news:u1eXq%23xiGHA.5036@.TK2MSFTNGP04.phx.gbl...
>|||OK, we figured out what the problem was for me. It appears that either I
hadn't accepted the terms or fully registered. I went back and logged in,
then clicked Manage Your Connect Profile in the lower left corner, accepted
the terms and completed the registration, and now after I've searched on a
string, below the results box I see a Submit Feedback button. If what you
want to provide feedback on cannot be found, click that button and submit
it.
Hope that helps,
Stephen Dybing
This posting is provided "AS IS" with no warranties, and confers no rights.
"Steve Dybing [MSFT]" <steve.dybing@.online.microsoft.com> wrote in messa
ge
news:eXbH$fkjGHA.3848@.TK2MSFTNGP04.phx.gbl...
> OK, the text has been cleaned up a little bit in the attempt to make it
> clear that you have to search for the issue before you can submit new
> feedback. This is done in the attempt to cut down on duplicates. Try the
> search to find out if it's already been reported and if not, if you have
> the ability to submit a new issue. I'll point out that it's not allowing
> me to yet, they're working on it...
> --
> Sincerely,
> Stephen Dybing
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> "Steve Dybing [MSFT]" <steve.dybing@.online.microsoft.com> wrote in mes
sage
> news:uR%23M$SkjGHA.4884@.TK2MSFTNGP03.phx.gbl...
>|||OK, we figured out what the problem was for me. It appears that either I
hadn't accepted the terms or fully registered. I went back and logged in,
then clicked Manage Your Connect Profile in the lower left corner, accepted
the terms and completed the registration, and now after I've searched on a
string, below the results box I see a Submit Feedback button. If what you
want to provide feedback on cannot be found, click that button and submit
it.
Hope that helps,
Stephen Dybing
This posting is provided "AS IS" with no warranties, and confers no rights.
"Steve Dybing [MSFT]" <steve.dybing@.online.microsoft.com> wrote in messa
ge
news:eXbH$fkjGHA.3848@.TK2MSFTNGP04.phx.gbl...
> OK, the text has been cleaned up a little bit in the attempt to make it
> clear that you have to search for the issue before you can submit new
> feedback. This is done in the attempt to cut down on duplicates. Try the
> search to find out if it's already been reported and if not, if you have
> the ability to submit a new issue. I'll point out that it's not allowing
> me to yet, they're working on it...
> --
> Sincerely,
> Stephen Dybing
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> "Steve Dybing [MSFT]" <steve.dybing@.online.microsoft.com> wrote in mes
sage
> news:uR%23M$SkjGHA.4884@.TK2MSFTNGP03.phx.gbl...
>|||Hello Steve,
"Steve Dybing [MSFT]" <steve.dybing@.online.microsoft.com> schrieb im
Newsbeitrag news:uR%23M$SkjGHA.4884@.TK2MSFTNGP03.phx.gbl...

> In the meantime, however, at the bottom of every KB article on the support
> site is a section that allows you to submit comments/bugs. Scroll to the
> bottom of http://support.microsoft.com/kb/918992/en-us and have a look.
> The support folks will be reading that information and can correct the
> article directly.
Great, that seems to have worked. It's just that I couldn't see it the first
time around, because on my browser of choice (Firefox) the lowest quarter of
the page doesn't get displayed (same problem with all kb entries).
Thank you and best regards,
Nils Loeber|||Hello Steve,
"Steve Dybing [MSFT]" <steve.dybing@.online.microsoft.com> schrieb im
Newsbeitrag news:uR%23M$SkjGHA.4884@.TK2MSFTNGP03.phx.gbl...

> In the meantime, however, at the bottom of every KB article on the support
> site is a section that allows you to submit comments/bugs. Scroll to the
> bottom of http://support.microsoft.com/kb/918992/en-us and have a look.
> The support folks will be reading that information and can correct the
> article directly.
Great, that seems to have worked. It's just that I couldn't see it the first
time around, because on my browser of choice (Firefox) the lowest quarter of
the page doesn't get displayed (same problem with all kb entries).
Thank you and best regards,
Nils Loeber|||After you connect to the site with Firefox, try doing a
refresh. I hit the same issue with the page displays and
that generally works for me.
-Sue
On Tue, 13 Jun 2006 12:22:59 +0200, "Nils Loeber"
<nils@.NOSPAMFORMEPLEASEnils-loeber.de> wrote:

>because on my browser of choice (Firefox) the lowest quarter of
>the page doesn't get displayed (same problem with all kb entries).