|
Home > Archive > microsoft.public.sqlserver.server > October 2002 > help!
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
|
| We have a very small office, 1- windows2000 SBS server,
and 3 computers. SBS comes with SQL included and we have
5 CALs (for win2k SBS) that inculdes licences to access
all the SBS features. So, 1 CAL gives 1 computer the
(legal) right to connect to the server, exchange, sql,
etc.
I have created a small SQL database on the server with
less than 500 records. Thanks to the help I got with my
previous post below I made an .asp page and have it
running on IIS (also on the SBS server). The ASP page
pulls info out of the SQL database, it is only
acccessible internally, and only to the 3 computers that
have licenses. So I should be legal right?
Now, I was trying to figure out how to make it accessible
on the web. Technically I know how, but I don't know how
that affects the licensing. It looks to me like what I
found here:
www.microsoft.com/sql/howtobuy/production.asp
means that I have to pay for a 5,000 dollar license (we
only have 1 processor). Is that right?
We are not making any money off of this and I cannot
afford to do it if that is true.
I would like to be able to give SOME other people access
to view some of the info in the database over the
internet, but not let them make changes to it.
Just trying to figure out how other people do this. It
seems pretty cost prohibitive, and I'd like to go on a
little rant about how it seems like MS bundled and
enterprise product with enterprise pricing in
their "small business" solution. But I really just want
to find out the best way to do this and stop wasting time.
Am I better off using Access? or MySQL?
If you were in my position what would you do?
Thanks,
Jason
| |
| Tibor Karaszi 2002-10-05, 9:09 pm |
| Jason,
To the best of my knowledge, you have interpreted the license agreement correctly. Here are a
couple of options to look into:
1. Generate the web pages using sp_makewebtask. See Books Online for more info.
2. You *might* get away using MSDE for this. MSDE comes with SQL Server and the license
agreement *might* allow you to use that in this situation. But you probably want to check with
your MS representative to be certain.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=...ublic.sqlserver
"Jason" <jasonmh26@hotmail.com> wrote in message
news:129a201c25b7b$f10496b0$35
ef2ecf@TKMSFTNGXA11...
> We have a very small office, 1- windows2000 SBS server,
> and 3 computers. SBS comes with SQL included and we have
> 5 CALs (for win2k SBS) that inculdes licences to access
> all the SBS features. So, 1 CAL gives 1 computer the
> (legal) right to connect to the server, exchange, sql,
> etc.
> I have created a small SQL database on the server with
> less than 500 records. Thanks to the help I got with my
> previous post below I made an .asp page and have it
> running on IIS (also on the SBS server). The ASP page
> pulls info out of the SQL database, it is only
> acccessible internally, and only to the 3 computers that
> have licenses. So I should be legal right?
> Now, I was trying to figure out how to make it accessible
> on the web. Technically I know how, but I don't know how
> that affects the licensing. It looks to me like what I
> found here:
> www.microsoft.com/sql/howtobuy/production.asp
> means that I have to pay for a 5,000 dollar license (we
> only have 1 processor). Is that right?
> We are not making any money off of this and I cannot
> afford to do it if that is true.
> I would like to be able to give SOME other people access
> to view some of the info in the database over the
> internet, but not let them make changes to it.
> Just trying to figure out how other people do this. It
> seems pretty cost prohibitive, and I'd like to go on a
> little rant about how it seems like MS bundled and
> enterprise product with enterprise pricing in
> their "small business" solution. But I really just want
> to find out the best way to do this and stop wasting time.
> Am I better off using Access? or MySQL?
> If you were in my position what would you do?
> Thanks,
> Jason
|
|
|
|
|