"Fredrik Wahlgren" <fredrik.p.wahlgren@mailbox.swipnet.se> wrote in message
news:OoXJ7g92EHA.1188@tk2msftngp13.phx.gbl...
>I want to add a few thoughts to my previous reply. As mentioned, my
> understanding is that if you connect to a remote server with either one of
> these intentions:
>
> 1) You need to copy a database in order to test your ADO.NET skills
>
> or
>
> 2) Connect to a database to see how it's doneMaybe you want to document
> each
> step
>
> you should be OK. If your intentions are beyond this, I think you need to
> set up a separate database that is completely decoupled from your
> production
> database. You may use a copy of your real database. This database must be
> set up in such a way that it is a test database. In addition, it should be
> on a different server so that your testing can't possibly interfere with
> your production database.
>
> Stephen, do you agree?
>
> / Fredrik
>
>
> "Kevin" <Kevin@discussions.microsoft.com> wrote in message
> news:F88222F0-2140-4DD6-B710-BFBB0CAD625D@microsoft.com...
>> Thanks for all the input. Not to beat a dead horse but here's my
> confusion...
>>
>> Assuming I can get this to connect, my reading of the license would be
> that
>> you can't use the database provided with the developer edition to be used
> as
>> a production database - which in my case would be to have my web site
> driven
>> directly from this database on my server. I don't plan to do that, but
>> instead need to connect to the fully licensed web server production
> database.
>> It seems that it would be OK for me to create a database locally and then
>> upload it the the web server, but the question is can I then use the
>> Developer Edition to make changes to this database as it sits on this web
>> server? The ambiguity here is what led to my original question - if this
>> edition does indeed allow you to connect to a remote database then my
>> assumption is that doing so would be legal under the license, but if it
>> is
>> not allowed then my guess is that the timeout error is the application's
>> somewhat crude way of letting me know that.
>>
>> "Kevin" wrote:
>>
>> > I just purchased SQL Server 2000 Developer Edition and want to use it
>> > to
>> > connect via TCP/IP to a SQL Server database located on a web host
> server.
>> > The application has the Client Network Utility and allows me to go
>> > about
>> > connecting, but I get a timeout error when I try to register to the
> remote
>> > database using the Enterprise Manager part of my SQL Server DE. My web
>> > hosting company so far has not been able to fix this. I am wondering if
> the
>> > problem is at their end or if the Developer Edition just isn't
>> > permitted
> to
>> > make this registration and the error is its way of telling me. I have
> read
>> > the license several times and scoured the documentation but don't see
> where
>> > this would not be allowed. Does anyone have any experience with this?
>
>

"Fredrik Wahlgren" <fredrik.p.wahlgren@mailbox.swipnet.se> wrote in message
news:OFtYfC%232EHA.3908@TK2MSFTNGP12.phx.gbl...
> It seems as we have come to road's end. I guess you have to follow
> Stephen's
> advice. I still feel that if you connect to a test database with test data
> and the sole intention of testing remote management, you should be OK.
>
> / Fredrik
>
>
> "Stephen Dybing [MSFT]" <stephd@online.microsoft.com> wrote in message
> news:41b4d1cc$1@news.microsoft.com...
>> I'm not comfortable getting that customer specific. I'm not a lawyer and
>> that answer really can only come from one. As such, Kevin, I'd be really
>> careful about taking advice from a newsgroup on legal issues like this.
> You
>> really need to talk to your lawyer, or at least start with someone from
> your
>> local Microsoft Sales office. :-(
>>
>> --
>> Sincerely,
>> Stephen Dybing
>>
>> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>> Please reply to the newsgroups only, thanks.
>> "Fredrik Wahlgren" <fredrik.p.wahlgren@mailbox.swipnet.se> wrote in
> message
>> news:OoXJ7g92EHA.1188@tk2msftngp13.phx.gbl...
>> >I want to add a few thoughts to my previous reply. As mentioned, my
>> > understanding is that if you connect to a remote server with either one
> of
>> > these intentions:
>> >
>> > 1) You need to copy a database in order to test your ADO.NET skills
>> >
>> > or
>> >
>> > 2) Connect to a database to see how it's doneMaybe you want to document
>> > each
>> > step
>> >
>> > you should be OK. If your intentions are beyond this, I think you need
> to
>> > set up a separate database that is completely decoupled from your
>> > production
>> > database. You may use a copy of your real database. This database must
> be
>> > set up in such a way that it is a test database. In addition, it should
> be
>> > on a different server so that your testing can't possibly interfere
>> > with
>> > your production database.
>> >
>> > Stephen, do you agree?
>> >
>> > / Fredrik
>> >
>> >
>> > "Kevin" <Kevin@discussions.microsoft.com> wrote in message
>> > news:F88222F0-2140-4DD6-B710-BFBB0CAD625D@microsoft.com...
>> >> Thanks for all the input. Not to beat a dead horse but here's my
>> > confusion...
>> >>
>> >> Assuming I can get this to connect, my reading of the license would be
>> > that
>> >> you can't use the database provided with the developer edition to be
> used
>> > as
>> >> a production database - which in my case would be to have my web site
>> > driven
>> >> directly from this database on my server. I don't plan to do that,
>> >> but
>> >> instead need to connect to the fully licensed web server production
>> > database.
>> >> It seems that it would be OK for me to create a database locally and
> then
>> >> upload it the the web server, but the question is can I then use the
>> >> Developer Edition to make changes to this database as it sits on this
> web
>> >> server? The ambiguity here is what led to my original question - if
> this
>> >> edition does indeed allow you to connect to a remote database then my
>> >> assumption is that doing so would be legal under the license, but if
>> >> it
>> >> is
>> >> not allowed then my guess is that the timeout error is the
> application's
>> >> somewhat crude way of letting me know that.
>> >>
>> >> "Kevin" wrote:
>> >>
>> >> > I just purchased SQL Server 2000 Developer Edition and want to use
>> >> > it
>> >> > to
>> >> > connect via TCP/IP to a SQL Server database located on a web host
>> > server.
>> >> > The application has the Client Network Utility and allows me to go
>> >> > about
>> >> > connecting, but I get a timeout error when I try to register to the
>> > remote
>> >> > database using the Enterprise Manager part of my SQL Server DE. My
> web
>> >> > hosting company so far has not been able to fix this. I am wondering
> if
>> > the
>> >> > problem is at their end or if the Developer Edition just isn't
>> >> > permitted
>> > to
>> >> > make this registration and the error is its way of telling me. I
> have
>> > read
>> >> > the license several times and scoured the documentation but don't
>> >> > see
>> > where
>> >> > this would not be allowed. Does anyone have any experience with
> this?
>> >
>> >
>>
>>
>
>

"Kevin" <Kevin@discussions.microsoft.com> wrote in message
news:40156020-1ACE-4021-94FD-2A0B10AFA7CD@microsoft.com...
> I just purchased SQL Server 2000 Developer Edition and want to use it to
> connect via TCP/IP to a SQL Server database located on a web host server.
> The application has the Client Network Utility and allows me to go about
> connecting, but I get a timeout error when I try to register to the remote
> database using the Enterprise Manager part of my SQL Server DE. My web
> hosting company so far has not been able to fix this. I am wondering if
the
> problem is at their end or if the Developer Edition just isn't permitted
to
> make this registration and the error is its way of telling me. I have
read
> the license several times and scoured the documentation but don't see
where
> this would not be allowed. Does anyone have any experience with this?

"Stephen Dybing [MSFT]" <stephd@online.microsoft.com> wrote in message
news:%23tkkcE82EHA.1264@TK2MSFTNGP12.phx.gbl...
> It should be permitted to connect but it may not be legal if you're
> attempting to use the Enterprise Manager from your Developer Edition to
> "manage" your database on the web host server. The Developer Editions is
> only licensed for designing, developing, and testing. Here's the FAQ from
> the SQL Server 2000 Licensing FAQ at
> http://www.microsoft.com/sql/howtobuy/faq.asp:
>
> Q. What is SQL Server 2000 Developer Edition and how is it licensed?
> A. SQL Server 2000 Developer Edition is licensed per developer and must
be
> used for designing, developing, and testing purposes only.
>
> I would double-check the connection string that your application is using
to
> make sure it's the same one you're attempting to use with Enterprise
> Manager.
>
> --
> Sincerely,
> Stephen Dybing
>
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> Please reply to the newsgroups only, thanks.
> "Kevin" <Kevin@discussions.microsoft.com> wrote in message
> news:40156020-1ACE-4021-94FD-2A0B10AFA7CD@microsoft.com...
> >I just purchased SQL Server 2000 Developer Edition and want to use it to
> > connect via TCP/IP to a SQL Server database located on a web host
server.
> > The application has the Client Network Utility and allows me to go about
> > connecting, but I get a timeout error when I try to register to the
remote
> > database using the Enterprise Manager part of my SQL Server DE. My web
> > hosting company so far has not been able to fix this. I am wondering if
> > the
> > problem is at their end or if the Developer Edition just isn't permitted
> > to
> > make this registration and the error is its way of telling me. I have
> > read
> > the license several times and scoured the documentation but don't see
> > where
> > this would not be allowed. Does anyone have any experience with this?
>
>

"Kevin" <Kevin@discussions.microsoft.com> wrote in message
news:F88222F0-2140-4DD6-B710-BFBB0CAD625D@microsoft.com...
> Thanks for all the input. Not to beat a dead horse but here's my
confusion...
>
> Assuming I can get this to connect, my reading of the license would be
that
> you can't use the database provided with the developer edition to be used
as
> a production database - which in my case would be to have my web site
driven
> directly from this database on my server.

> I don't plan to do that, but
> instead need to connect to the fully licensed web server production
database.
> It seems that it would be OK for me to create a database locally and then
> upload it the the web server, but the question is can I then use the
> Developer Edition to make changes to this database as it sits on this web
> server?

> The ambiguity here is what led to my original question - if this
> edition does indeed allow you to connect to a remote database then my
> assumption is that doing so would be legal under the license, but if it is
> not allowed then my guess is that the timeout error is the application's
> somewhat crude way of letting me know that.

>
> "Kevin" wrote:
>
> > I just purchased SQL Server 2000 Developer Edition and want to use it to
> > connect via TCP/IP to a SQL Server database located on a web host
server.
> > The application has the Client Network Utility and allows me to go about

> > connecting, but I get a timeout error when I try to register to the
remote
> > database using the Enterprise Manager part of my SQL Server DE. My web
> > hosting company so far has not been able to fix this. I am wondering if
the
> > problem is at their end or if the Developer Edition just isn't permitted
to
> > make this registration and the error is its way of telling me. I have
read
> > the license several times and scoured the documentation but don't see
where
> > this would not be allowed. Does anyone have any experience with this?

"Kevin" <Kevin@discussions.microsoft.com> wrote in message
news:F88222F0-2140-4DD6-B710-BFBB0CAD625D@microsoft.com...
> Thanks for all the input. Not to beat a dead horse but here's my
confusion...
>
> Assuming I can get this to connect, my reading of the license would be
that
> you can't use the database provided with the developer edition to be used
as
> a production database - which in my case would be to have my web site
driven
> directly from this database on my server. I don't plan to do that, but
> instead need to connect to the fully licensed web server production
database.
> It seems that it would be OK for me to create a database locally and then
> upload it the the web server, but the question is can I then use the
> Developer Edition to make changes to this database as it sits on this web
> server? The ambiguity here is what led to my original question - if this
> edition does indeed allow you to connect to a remote database then my
> assumption is that doing so would be legal under the license, but if it is
> not allowed then my guess is that the timeout error is the application's
> somewhat crude way of letting me know that.
>
> "Kevin" wrote:
>
> > I just purchased SQL Server 2000 Developer Edition and want to use it to
> > connect via TCP/IP to a SQL Server database located on a web host
server.
> > The application has the Client Network Utility and allows me to go about
> > connecting, but I get a timeout error when I try to register to the
remote
> > database using the Enterprise Manager part of my SQL Server DE. My web
> > hosting company so far has not been able to fix this. I am wondering if
the
> > problem is at their end or if the Developer Edition just isn't permitted
to
> > make this registration and the error is its way of telling me. I have
read
> > the license several times and scoured the documentation but don't see
where
> > this would not be allowed. Does anyone have any experience with this?

"Stephen Dybing [MSFT]" <stephd@online.microsoft.com> wrote in message
news:41b4d1cc$1@news.microsoft.com...
> I'm not comfortable getting that customer specific. I'm not a lawyer and
> that answer really can only come from one. As such, Kevin, I'd be really
> careful about taking advice from a newsgroup on legal issues like this.
You
> really need to talk to your lawyer, or at least start with someone from
your
> local Microsoft Sales office. :-(
>
> --
> Sincerely,
> Stephen Dybing
>
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> Please reply to the newsgroups only, thanks.
> "Fredrik Wahlgren" <fredrik.p.wahlgren@mailbox.swipnet.se> wrote in
message
> news:OoXJ7g92EHA.1188@tk2msftngp13.phx.gbl...
> >I want to add a few thoughts to my previous reply. As mentioned, my
> > understanding is that if you connect to a remote server with either one
of
> > these intentions:
> >
> > 1) You need to copy a database in order to test your ADO.NET skills
> >
> > or
> >
> > 2) Connect to a database to see how it's doneMaybe you want to document
> > each
> > step
> >
> > you should be OK. If your intentions are beyond this, I think you need
to
> > set up a separate database that is completely decoupled from your
> > production
> > database. You may use a copy of your real database. This database must
be
> > set up in such a way that it is a test database. In addition, it should
be
> > on a different server so that your testing can't possibly interfere with
> > your production database.
> >
> > Stephen, do you agree?
> >
> > / Fredrik
> >
> >
> > "Kevin" <Kevin@discussions.microsoft.com> wrote in message
> > news:F88222F0-2140-4DD6-B710-BFBB0CAD625D@microsoft.com...
> >> Thanks for all the input. Not to beat a dead horse but here's my
> > confusion...
> >>
> >> Assuming I can get this to connect, my reading of the license would be
> > that
> >> you can't use the database provided with the developer edition to be
used
> > as
> >> a production database - which in my case would be to have my web site
> > driven
> >> directly from this database on my server. I don't plan to do that, but
> >> instead need to connect to the fully licensed web server production
> > database.
> >> It seems that it would be OK for me to create a database locally and
then
> >> upload it the the web server, but the question is can I then use the
> >> Developer Edition to make changes to this database as it sits on this
web
> >> server? The ambiguity here is what led to my original question - if
this
> >> edition does indeed allow you to connect to a remote database then my
> >> assumption is that doing so would be legal under the license, but if it
> >> is
> >> not allowed then my guess is that the timeout error is the
application's
> >> somewhat crude way of letting me know that.
> >>
> >> "Kevin" wrote:
> >>
> >> > I just purchased SQL Server 2000 Developer Edition and want to use it
> >> > to
> >> > connect via TCP/IP to a SQL Server database located on a web host
> > server.
> >> > The application has the Client Network Utility and allows me to go
> >> > about
> >> > connecting, but I get a timeout error when I try to register to the
> > remote
> >> > database using the Enterprise Manager part of my SQL Server DE. My
web
> >> > hosting company so far has not been able to fix this. I am wondering
if
> > the
> >> > problem is at their end or if the Developer Edition just isn't
> >> > permitted
> > to
> >> > make this registration and the error is its way of telling me. I
have
> > read
> >> > the license several times and scoured the documentation but don't see
> > where
> >> > this would not be allowed. Does anyone have any experience with
this?
> >
> >
>
>

"Stephen Dybing [MSFT]" <stephd@online.microsoft.com> wrote in message
news:41b4dc0e$1@news.microsoft.com...
> Right, sorry, I agree with that. Testing really goes along with
development,
> or at least it had better. :-) My concern is that wasn't what the
intentions
> were.
>
> --
> Sincerely,
> Stephen Dybing
>
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> Please reply to the newsgroups only, thanks.
> "Fredrik Wahlgren" <fredrik.p.wahlgren@mailbox.swipnet.se> wrote in
message
> news:OFtYfC%232EHA.3908@TK2MSFTNGP12.phx.gbl...
> > It seems as we have come to road's end. I guess you have to follow
> > Stephen's
> > advice. I still feel that if you connect to a test database with test
data
> > and the sole intention of testing remote management, you should be OK.
> >
> > / Fredrik
> >
> >
> > "Stephen Dybing [MSFT]" <stephd@online.microsoft.com> wrote in message
> > news:41b4d1cc$1@news.microsoft.com...
> >> I'm not comfortable getting that customer specific. I'm not a lawyer
and
> >> that answer really can only come from one. As such, Kevin, I'd be
really
> >> careful about taking advice from a newsgroup on legal issues like this.
> > You
> >> really need to talk to your lawyer, or at least start with someone from
> > your
> >> local Microsoft Sales office. :-(
> >>
> >> --
> >> Sincerely,
> >> Stephen Dybing
> >>
> >> This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> >> Please reply to the newsgroups only, thanks.
> >> "Fredrik Wahlgren" <fredrik.p.wahlgren@mailbox.swipnet.se> wrote in
> > message
> >> news:OoXJ7g92EHA.1188@tk2msftngp13.phx.gbl...
> >> >I want to add a few thoughts to my previous reply. As mentioned, my
> >> > understanding is that if you connect to a remote server with either
one
> > of
> >> > these intentions:
> >> >
> >> > 1) You need to copy a database in order to test your ADO.NET skills
> >> >
> >> > or
> >> >
> >> > 2) Connect to a database to see how it's doneMaybe you want to
document
> >> > each
> >> > step
> >> >
> >> > you should be OK. If your intentions are beyond this, I think you
need
> > to
> >> > set up a separate database that is completely decoupled from your
> >> > production
> >> > database. You may use a copy of your real database. This database
must
> > be
> >> > set up in such a way that it is a test database. In addition, it
should
> > be
> >> > on a different server so that your testing can't possibly interfere
> >> > with
> >> > your production database.
> >> >
> >> > Stephen, do you agree?
> >> >
> >> > / Fredrik
> >> >
> >> >
> >> > "Kevin" <Kevin@discussions.microsoft.com> wrote in message
> >> > news:F88222F0-2140-4DD6-B710-BFBB0CAD625D@microsoft.com...
> >> >> Thanks for all the input. Not to beat a dead horse but here's my
> >> > confusion...
> >> >>
> >> >> Assuming I can get this to connect, my reading of the license would
be
> >> > that
> >> >> you can't use the database provided with the developer edition to be
> > used
> >> > as
> >> >> a production database - which in my case would be to have my web
site
> >> > driven
> >> >> directly from this database on my server. I don't plan to do that,
> >> >> but
> >> >> instead need to connect to the fully licensed web server production
> >> > database.
> >> >> It seems that it would be OK for me to create a database locally and
> > then
> >> >> upload it the the web server, but the question is can I then use the
> >> >> Developer Edition to make changes to this database as it sits on
this
> > web
> >> >> server? The ambiguity here is what led to my original question - if
> > this
> >> >> edition does indeed allow you to connect to a remote database then
my
> >> >> assumption is that doing so would be legal under the license, but if
> >> >> it
> >> >> is
> >> >> not allowed then my guess is that the timeout error is the
> > application's
> >> >> somewhat crude way of letting me know that.
> >> >>
> >> >> "Kevin" wrote:
> >> >>
> >> >> > I just purchased SQL Server 2000 Developer Edition and want to use
> >> >> > it
> >> >> > to
> >> >> > connect via TCP/IP to a SQL Server database located on a web host
> >> > server.
> >> >> > The application has the Client Network Utility and allows me to go
> >> >> > about
> >> >> > connecting, but I get a timeout error when I try to register to
the
> >> > remote
> >> >> > database using the Enterprise Manager part of my SQL Server DE. My
> > web
> >> >> > hosting company so far has not been able to fix this. I am
wondering
> > if
> >> > the
> >> >> > problem is at their end or if the Developer Edition just isn't
> >> >> > permitted
> >> > to
> >> >> > make this registration and the error is its way of telling me. I
> > have
> >> > read
> >> >> > the license several times and scoured the documentation but don't
> >> >> > see
> >> > where
> >> >> > this would not be allowed. Does anyone have any experience with
> > this?
> >> >
> >> >
> >>
> >>
> >
> >
>
>

<Kevin@discussions.microsoft.com> wrote:

>I just purchased SQL Server 2000 Developer Edition and want to use it to
>connect via TCP/IP to a SQL Server database located on a web host server.
>The application has the Client Network Utility and allows me to go about
>connecting, but I get a timeout error when I try to register to the remote
>database using the Enterprise Manager part of my SQL Server DE. My web
>hosting company so far has not been able to fix this. I am wondering if the
>problem is at their end or if the Developer Edition just isn't permitted to
>make this registration and the error is its way of telling me. I have read
>the license several times and scoured the documentation but don't see where
>this would not be allowed. Does anyone have any experience with this?