somewhat lacking in DTS wizard in 2005 Standard Management Studio ?
were did it go : (
scottScott,
you can right-click a database, select "Tasks" and the "Import Data"/"Export
Data".
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com|||On Feb 27, 9:20 am, "Scott" <s...@.yahoo.com> wrote:
> somewhat lacking in DTS wizard in 2005 Standard Management Studio ?
> were did it go : (
> scott
DTS no longer exists, it has been replaced with SQL Server Integration
Services (SSIS).
Showing posts with label wizard. Show all posts
Showing posts with label wizard. Show all posts
Saturday, February 25, 2012
2005 stand DTS ?
somewhat lacking in DTS wizard in 2005 Standard Management Studio ?
were did it go : (
scott
Scott,
you can right-click a database, select "Tasks" and the "Import Data"/"Export
Data".
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
|||On Feb 27, 9:20 am, "Scott" <s...@.yahoo.com> wrote:
> somewhat lacking in DTS wizard in 2005 Standard Management Studio ?
> were did it go : (
> scott
DTS no longer exists, it has been replaced with SQL Server Integration
Services (SSIS).
were did it go : (
scott
Scott,
you can right-click a database, select "Tasks" and the "Import Data"/"Export
Data".
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
|||On Feb 27, 9:20 am, "Scott" <s...@.yahoo.com> wrote:
> somewhat lacking in DTS wizard in 2005 Standard Management Studio ?
> were did it go : (
> scott
DTS no longer exists, it has been replaced with SQL Server Integration
Services (SSIS).
2005 stand DTS ?
somewhat lacking in DTS wizard in 2005 Standard Management Studio ?
were did it go : (
scottScott,
you can right-click a database, select "Tasks" and the "Import Data"/"Export
Data".
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com|||On Feb 27, 9:20 am, "Scott" <s...@.yahoo.com> wrote:
> somewhat lacking in DTS wizard in 2005 Standard Management Studio ?
> were did it go : (
> scott
DTS no longer exists, it has been replaced with SQL Server Integration
Services (SSIS).
were did it go : (
scottScott,
you can right-click a database, select "Tasks" and the "Import Data"/"Export
Data".
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com|||On Feb 27, 9:20 am, "Scott" <s...@.yahoo.com> wrote:
> somewhat lacking in DTS wizard in 2005 Standard Management Studio ?
> were did it go : (
> scott
DTS no longer exists, it has been replaced with SQL Server Integration
Services (SSIS).
2005 SP2: failed to modify maintenance paln
After upgrading to SP2, I created a maintenance plan in the management studio using the wizard. The plan executes OK. But when I tried to modify it, I got the following error, and cannot load and modify:
Value cannot be null.
Parameter name: component (System.Design)
Please help ASAP.
Ed
Can you please submit this as a defect on Microsoft Connect? Please include steps to reproduce the problem, screen shots, and as much details information about the error message (sometimes you can copy the "stack trace" which is very useful to our dev team).
Microsoft Connect:
http://connect.microsoft.com/SQLServer/Feedback/
Paul A. Mestemaker II
Program Manager
Microsoft SQL Server Manageability
http://blogs.msdn.com/sqlrem/
2005 SP2: failed to modify maintenance paln
After upgrading to SP2, I created a maintenance plan in the management studio using the wizard. The plan executes OK. But when I tried to modify it, I got the following error, and cannot load and modify:
Value cannot be null.
Parameter name: component (System.Design)
Please help ASAP.
Ed
Can you please submit this as a defect on Microsoft Connect? Please include steps to reproduce the problem, screen shots, and as much details information about the error message (sometimes you can copy the "stack trace" which is very useful to our dev team).
Microsoft Connect:
http://connect.microsoft.com/SQLServer/Feedback/
Paul A. Mestemaker II
Program Manager
Microsoft SQL Server Manageability
http://blogs.msdn.com/sqlrem/
Friday, February 24, 2012
2005 replication subscriber can't see 2000 publisher - why?
I enabled publishing on the SQL 2000 box so that I can do replication from
2000 to 2005. During the wizard setup, the 2005 subscriber gets this error:
---
Cannot connect to Server1. Additional information: Failed to connection to
server Server1 (Microsoft.SqlServer.ConnectionInfo) An error has occurred
while establishing a connection tot he server. When connecting to SQL
Server 2005, this failure may be caused by the fact that under the default
settings SQL Server does not allow remote connections. (provider: Named
Pipes Provider, error 40 - Could not open a connection to SQL Server)
(Microsoft SQL Server, Error: 52).
---
Both boxes are on the same LAN subnet with no firewall between them. I
added an entry to my HOSTS file on the 2005 server so it can see the 2000
server by name (the wizard won't let you type in an IP address). Pinging
that machine works fine.
I don't know why this happens. I've tried windows auth and SQL auth.
What's the trick? Is 2005 using some new communications method that 2000
doesn't understand? I don't even know of a log file that would help but
maybe someone knows the answer or where there is some log info.Open the Surface Area Configuration on the 2005 machine and enable remote
connections. By default a newly installed SQL Server 2005 instance will
only respond to requests sent from the physical machine it was installed on.
--
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"HK" <replywithingroup@.notreal.com> wrote in message
news:ZSbKf.13005$Ou1.8109@.tornado.socal.rr.com...
>I enabled publishing on the SQL 2000 box so that I can do replication from
> 2000 to 2005. During the wizard setup, the 2005 subscriber gets this
> error:
> ---
> Cannot connect to Server1. Additional information: Failed to connection
> to
> server Server1 (Microsoft.SqlServer.ConnectionInfo) An error has occurred
> while establishing a connection tot he server. When connecting to SQL
> Server 2005, this failure may be caused by the fact that under the default
> settings SQL Server does not allow remote connections. (provider: Named
> Pipes Provider, error 40 - Could not open a connection to SQL Server)
> (Microsoft SQL Server, Error: 52).
> ---
> Both boxes are on the same LAN subnet with no firewall between them. I
> added an entry to my HOSTS file on the 2005 server so it can see the 2000
> server by name (the wizard won't let you type in an IP address). Pinging
> that machine works fine.
> I don't know why this happens. I've tried windows auth and SQL auth.
> What's the trick? Is 2005 using some new communications method that 2000
> doesn't understand? I don't even know of a log file that would help but
> maybe someone knows the answer or where there is some log info.
>|||On the subscriber machine? That sounds like something I would do on the
publisher but the publisher is SQL 2000.
"Michael Hotek" <mike@.solidqualitylearning.com> wrote in message
news:uHHA4ZpNGHA.3460@.TK2MSFTNGP15.phx.gbl...
> Open the Surface Area Configuration on the 2005 machine and enable remote
> connections. By default a newly installed SQL Server 2005 instance will
> only respond to requests sent from the physical machine it was installed
on.
> --
> Mike
> http://www.solidqualitylearning.com
> Disclaimer: This communication is an original work and represents my sole
> views on the subject. It does not represent the views of any other person
> or entity either by inference or direct reference.
>
> "HK" <replywithingroup@.notreal.com> wrote in message
> news:ZSbKf.13005$Ou1.8109@.tornado.socal.rr.com...
> >I enabled publishing on the SQL 2000 box so that I can do replication
from
> > 2000 to 2005. During the wizard setup, the 2005 subscriber gets this
> > error:
> >
> > ---
> > Cannot connect to Server1. Additional information: Failed to
connection
> > to
> > server Server1 (Microsoft.SqlServer.ConnectionInfo) An error has
occurred
> > while establishing a connection tot he server. When connecting to SQL
> > Server 2005, this failure may be caused by the fact that under the
default
> > settings SQL Server does not allow remote connections. (provider:
Named
> > Pipes Provider, error 40 - Could not open a connection to SQL Server)
> > (Microsoft SQL Server, Error: 52).
> > ---
> >
> > Both boxes are on the same LAN subnet with no firewall between them. I
> > added an entry to my HOSTS file on the 2005 server so it can see the
2000
> > server by name (the wizard won't let you type in an IP address).
Pinging
> > that machine works fine.
> >
> > I don't know why this happens. I've tried windows auth and SQL auth.
> > What's the trick? Is 2005 using some new communications method that
2000
> > doesn't understand? I don't even know of a log file that would help but
> > maybe someone knows the answer or where there is some log info.
> >
> >
>|||The setting Mike told you about is to allow the remote machine (publisher)
to connect to the local (Subscriber - 2005) machine. It is from the
viewpoint of the 2005 machine.
--
Andrew J. Kelly SQL MVP
"HK" <replywithingroup@.notreal.com> wrote in message
news:J9HKf.8983$Jg.197@.tornado.socal.rr.com...
> On the subscriber machine? That sounds like something I would do on the
> publisher but the publisher is SQL 2000.
> "Michael Hotek" <mike@.solidqualitylearning.com> wrote in message
> news:uHHA4ZpNGHA.3460@.TK2MSFTNGP15.phx.gbl...
>> Open the Surface Area Configuration on the 2005 machine and enable remote
>> connections. By default a newly installed SQL Server 2005 instance will
>> only respond to requests sent from the physical machine it was installed
> on.
>> --
>> Mike
>> http://www.solidqualitylearning.com
>> Disclaimer: This communication is an original work and represents my sole
>> views on the subject. It does not represent the views of any other
>> person
>> or entity either by inference or direct reference.
>>
>> "HK" <replywithingroup@.notreal.com> wrote in message
>> news:ZSbKf.13005$Ou1.8109@.tornado.socal.rr.com...
>> >I enabled publishing on the SQL 2000 box so that I can do replication
> from
>> > 2000 to 2005. During the wizard setup, the 2005 subscriber gets this
>> > error:
>> >
>> > ---
>> > Cannot connect to Server1. Additional information: Failed to
> connection
>> > to
>> > server Server1 (Microsoft.SqlServer.ConnectionInfo) An error has
> occurred
>> > while establishing a connection tot he server. When connecting to SQL
>> > Server 2005, this failure may be caused by the fact that under the
> default
>> > settings SQL Server does not allow remote connections. (provider:
> Named
>> > Pipes Provider, error 40 - Could not open a connection to SQL Server)
>> > (Microsoft SQL Server, Error: 52).
>> > ---
>> >
>> > Both boxes are on the same LAN subnet with no firewall between them. I
>> > added an entry to my HOSTS file on the 2005 server so it can see the
> 2000
>> > server by name (the wizard won't let you type in an IP address).
> Pinging
>> > that machine works fine.
>> >
>> > I don't know why this happens. I've tried windows auth and SQL auth.
>> > What's the trick? Is 2005 using some new communications method that
> 2000
>> > doesn't understand? I don't even know of a log file that would help
>> > but
>> > maybe someone knows the answer or where there is some log info.
>> >
>> >
>>
>
2000 to 2005. During the wizard setup, the 2005 subscriber gets this error:
---
Cannot connect to Server1. Additional information: Failed to connection to
server Server1 (Microsoft.SqlServer.ConnectionInfo) An error has occurred
while establishing a connection tot he server. When connecting to SQL
Server 2005, this failure may be caused by the fact that under the default
settings SQL Server does not allow remote connections. (provider: Named
Pipes Provider, error 40 - Could not open a connection to SQL Server)
(Microsoft SQL Server, Error: 52).
---
Both boxes are on the same LAN subnet with no firewall between them. I
added an entry to my HOSTS file on the 2005 server so it can see the 2000
server by name (the wizard won't let you type in an IP address). Pinging
that machine works fine.
I don't know why this happens. I've tried windows auth and SQL auth.
What's the trick? Is 2005 using some new communications method that 2000
doesn't understand? I don't even know of a log file that would help but
maybe someone knows the answer or where there is some log info.Open the Surface Area Configuration on the 2005 machine and enable remote
connections. By default a newly installed SQL Server 2005 instance will
only respond to requests sent from the physical machine it was installed on.
--
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"HK" <replywithingroup@.notreal.com> wrote in message
news:ZSbKf.13005$Ou1.8109@.tornado.socal.rr.com...
>I enabled publishing on the SQL 2000 box so that I can do replication from
> 2000 to 2005. During the wizard setup, the 2005 subscriber gets this
> error:
> ---
> Cannot connect to Server1. Additional information: Failed to connection
> to
> server Server1 (Microsoft.SqlServer.ConnectionInfo) An error has occurred
> while establishing a connection tot he server. When connecting to SQL
> Server 2005, this failure may be caused by the fact that under the default
> settings SQL Server does not allow remote connections. (provider: Named
> Pipes Provider, error 40 - Could not open a connection to SQL Server)
> (Microsoft SQL Server, Error: 52).
> ---
> Both boxes are on the same LAN subnet with no firewall between them. I
> added an entry to my HOSTS file on the 2005 server so it can see the 2000
> server by name (the wizard won't let you type in an IP address). Pinging
> that machine works fine.
> I don't know why this happens. I've tried windows auth and SQL auth.
> What's the trick? Is 2005 using some new communications method that 2000
> doesn't understand? I don't even know of a log file that would help but
> maybe someone knows the answer or where there is some log info.
>|||On the subscriber machine? That sounds like something I would do on the
publisher but the publisher is SQL 2000.
"Michael Hotek" <mike@.solidqualitylearning.com> wrote in message
news:uHHA4ZpNGHA.3460@.TK2MSFTNGP15.phx.gbl...
> Open the Surface Area Configuration on the 2005 machine and enable remote
> connections. By default a newly installed SQL Server 2005 instance will
> only respond to requests sent from the physical machine it was installed
on.
> --
> Mike
> http://www.solidqualitylearning.com
> Disclaimer: This communication is an original work and represents my sole
> views on the subject. It does not represent the views of any other person
> or entity either by inference or direct reference.
>
> "HK" <replywithingroup@.notreal.com> wrote in message
> news:ZSbKf.13005$Ou1.8109@.tornado.socal.rr.com...
> >I enabled publishing on the SQL 2000 box so that I can do replication
from
> > 2000 to 2005. During the wizard setup, the 2005 subscriber gets this
> > error:
> >
> > ---
> > Cannot connect to Server1. Additional information: Failed to
connection
> > to
> > server Server1 (Microsoft.SqlServer.ConnectionInfo) An error has
occurred
> > while establishing a connection tot he server. When connecting to SQL
> > Server 2005, this failure may be caused by the fact that under the
default
> > settings SQL Server does not allow remote connections. (provider:
Named
> > Pipes Provider, error 40 - Could not open a connection to SQL Server)
> > (Microsoft SQL Server, Error: 52).
> > ---
> >
> > Both boxes are on the same LAN subnet with no firewall between them. I
> > added an entry to my HOSTS file on the 2005 server so it can see the
2000
> > server by name (the wizard won't let you type in an IP address).
Pinging
> > that machine works fine.
> >
> > I don't know why this happens. I've tried windows auth and SQL auth.
> > What's the trick? Is 2005 using some new communications method that
2000
> > doesn't understand? I don't even know of a log file that would help but
> > maybe someone knows the answer or where there is some log info.
> >
> >
>|||The setting Mike told you about is to allow the remote machine (publisher)
to connect to the local (Subscriber - 2005) machine. It is from the
viewpoint of the 2005 machine.
--
Andrew J. Kelly SQL MVP
"HK" <replywithingroup@.notreal.com> wrote in message
news:J9HKf.8983$Jg.197@.tornado.socal.rr.com...
> On the subscriber machine? That sounds like something I would do on the
> publisher but the publisher is SQL 2000.
> "Michael Hotek" <mike@.solidqualitylearning.com> wrote in message
> news:uHHA4ZpNGHA.3460@.TK2MSFTNGP15.phx.gbl...
>> Open the Surface Area Configuration on the 2005 machine and enable remote
>> connections. By default a newly installed SQL Server 2005 instance will
>> only respond to requests sent from the physical machine it was installed
> on.
>> --
>> Mike
>> http://www.solidqualitylearning.com
>> Disclaimer: This communication is an original work and represents my sole
>> views on the subject. It does not represent the views of any other
>> person
>> or entity either by inference or direct reference.
>>
>> "HK" <replywithingroup@.notreal.com> wrote in message
>> news:ZSbKf.13005$Ou1.8109@.tornado.socal.rr.com...
>> >I enabled publishing on the SQL 2000 box so that I can do replication
> from
>> > 2000 to 2005. During the wizard setup, the 2005 subscriber gets this
>> > error:
>> >
>> > ---
>> > Cannot connect to Server1. Additional information: Failed to
> connection
>> > to
>> > server Server1 (Microsoft.SqlServer.ConnectionInfo) An error has
> occurred
>> > while establishing a connection tot he server. When connecting to SQL
>> > Server 2005, this failure may be caused by the fact that under the
> default
>> > settings SQL Server does not allow remote connections. (provider:
> Named
>> > Pipes Provider, error 40 - Could not open a connection to SQL Server)
>> > (Microsoft SQL Server, Error: 52).
>> > ---
>> >
>> > Both boxes are on the same LAN subnet with no firewall between them. I
>> > added an entry to my HOSTS file on the 2005 server so it can see the
> 2000
>> > server by name (the wizard won't let you type in an IP address).
> Pinging
>> > that machine works fine.
>> >
>> > I don't know why this happens. I've tried windows auth and SQL auth.
>> > What's the trick? Is 2005 using some new communications method that
> 2000
>> > doesn't understand? I don't even know of a log file that would help
>> > but
>> > maybe someone knows the answer or where there is some log info.
>> >
>> >
>>
>
Monday, February 13, 2012
2005 Express: testing replication
Hello,
I am learning SQL Server 2005 Express. I need to test replication but
when I run New Subscription Wizard I got error: "There are no
publications to which you can subscribe, either because this server
has no publications or because you do not have sufficient privileges
to access the publications."
I see no option for publications. Does this mean that in Express I
cannot run replication? If I can, how?
Thank you very much
/RAM/Am Fri, 07 Jul 2006 13:59:23 +0200 schrieb R.A.M.:
SQLExpress can use Replication, but only as subscriber. And your message
says, SQLExpress cannot access the publisher. Do you have a publisher
running? Publisher cannot be done with SQLExpress.
>
>SQLExpress can use Replication, but only as subscriber. And your message
>says, SQLExpress cannot access the publisher. Do you have a publisher
>running? Publisher cannot be done with SQLExpress.
>
>bye, Helmut
thank you
no, I have only Express Edition.
pity.
BTW, is Replication and Data Mirroring the same thing?
Hmm, i am no expert for this. As much as i know is, that data mirroring
means it happens in real time, so you can switch with no delay from one
server to the other one. Replikation goes in intervals, between the
intervals data between the two databases is different. But i am not sure if
this is the right definition.
No.
I am learning SQL Server 2005 Express. I need to test replication but
when I run New Subscription Wizard I got error: "There are no
publications to which you can subscribe, either because this server
has no publications or because you do not have sufficient privileges
to access the publications."
I see no option for publications. Does this mean that in Express I
cannot run replication? If I can, how?
Thank you very much
/RAM/Am Fri, 07 Jul 2006 13:59:23 +0200 schrieb R.A.M.:
Quote:
Originally Posted by
Hello,
I am learning SQL Server 2005 Express. I need to test replication but
when I run New Subscription Wizard I got error: "There are no
publications to which you can subscribe, either because this server
has no publications or because you do not have sufficient privileges
to access the publications."
I see no option for publications. Does this mean that in Express I
cannot run replication? If I can, how?
Thank you very much
/RAM/
SQLExpress can use Replication, but only as subscriber. And your message
says, SQLExpress cannot access the publisher. Do you have a publisher
running? Publisher cannot be done with SQLExpress.
bye, Helmut|||On Fri, 7 Jul 2006 14:55:16 +0200, Helmut Woess <user22@.inode.at>
wrote:
Quote:
Originally Posted by
>Am Fri, 07 Jul 2006 13:59:23 +0200 schrieb R.A.M.:
>
Quote:
Originally Posted by
>Hello,
>I am learning SQL Server 2005 Express. I need to test replication but
>when I run New Subscription Wizard I got error: "There are no
>publications to which you can subscribe, either because this server
>has no publications or because you do not have sufficient privileges
>to access the publications."
>I see no option for publications. Does this mean that in Express I
>cannot run replication? If I can, how?
>Thank you very much
>/RAM/
>
>SQLExpress can use Replication, but only as subscriber. And your message
>says, SQLExpress cannot access the publisher. Do you have a publisher
>running? Publisher cannot be done with SQLExpress.
>
>bye, Helmut
thank you
no, I have only Express Edition.
pity.
BTW, is Replication and Data Mirroring the same thing?
/RAM/|||Am Fri, 07 Jul 2006 16:05:09 +0200 schrieb R.A.M.:
...
Quote:
Originally Posted by
BTW, is Replication and Data Mirroring the same thing?
>
/RAM/
Hmm, i am no expert for this. As much as i know is, that data mirroring
means it happens in real time, so you can switch with no delay from one
server to the other one. Replikation goes in intervals, between the
intervals data between the two databases is different. But i am not sure if
this is the right definition.
bye, Helmut|||"R.A.M." <r_ahimsa_m@.poczta.onet.plwrote in message
news:v7qsa2tmij36hi65heqv02j8p52t59nesi@.4ax.com...
Quote:
Originally Posted by
On Fri, 7 Jul 2006 14:55:16 +0200, Helmut Woess <user22@.inode.at>
wrote:
>
thank you
no, I have only Express Edition.
pity.
BTW, is Replication and Data Mirroring the same thing?
No.
Quote:
Originally Posted by
>
/RAM/
>
Subscribe to:
Posts (Atom)