Re: Licensing - rumours and flotsam floating around my company. What's the status?
- From: "Darren Shaffer" <darrenshaffer@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 22 Jun 2005 09:59:27 -0600
the only licensing requirement for SQL Server CE
is that when you are replicating to a SQL Server 2000
database which is not licensed per processor
(in other words, you're on CAL licensing), you need
a CAL for each SQL CE client which will replicate
with the server. you are using CPU licensing, so
no CAL is required.
I'd suggest you consider porting your app to SQLMobile
and use VS2005 C++ Smart Device Projects rather than
SQL CE 2 and eVC. Same licensing model applies for
SQLMobile.
--
Darren Shaffer
..NET Compact Framework MVP
Principal Architect
Connected Innovation
www.connectedinnovation.com
"Keld Laursen" <kl@xxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:O9W3GbzdFHA.796@xxxxxxxxxxxxxxxxxxxxxxx
> Hi, all.
>
> I am currentlu porting an application from eVB to Ce.NET. In the process I
> want to go to SQL Server CE for my database needs.
> Due to some unclear wording on the licensing page some co-workers are very
> afraid about licensing fees for SSCE.
>
> My setup is this:
> I have a bunch of PDAs that will run SSCE. These PDAs will sync data
> against some Access database on a local PC.
> When the product is mature enough, it will sync data against an SQL server
> somewhere on the Internet. This SQL server is per-processor licensed.
> The intended sync path for the application is towards either an non-SS2000
> database or towards a per-processor-licensed SS2000 database.
>
> As far as I can read the license, this shouldn't call for a CAL for each
> PDA, but here comes the flotsam and rumours:
> If some user elects to port some data to another SS2000 database (per-seat
> licensed) using whatever means (like copying data from the local Access
> database to the SS2000 or just entering data read from the PDA screen ),
> the CAL should immediately be called for.
> If data from the SSCE system is delivered (via the local PC's Access
> database) to 3rd parties using unknown database systems, a CAL is called
> for, just in case they use a SS2000? (This could be the case when
> consolidated data is reported to e.g. government agencies). If this case
> calls for a CAL, then the word in many cases would be: Forget running for
> free as your data will eventually end up on a 3rd party system that
> *might* use an SQL server that requires you to get a CAL.
>
> What's the truth regarding this? Will I (my application) be liable for
> unintended uses - or for intended uses towards systems outside of my
> control?
>
> Best regards,
>
> Keld Laursen
> Danish Agricultural Advisory Services
> National Centre
>
.
- Follow-Ups:
- References:
- Prev by Date: Re: Trouble in opening prior SQL CE database on SQL Mobile
- Next by Date: Re: RDA
- Previous by thread: Licensing - rumours and flotsam floating around my company. What's the status?
- Next by thread: Re: Licensing - rumours and flotsam floating around my company. What's the status?
- Index(es):
Relevant Pages
|
