1) If I have a mobile application database written in SQL Server which has SQL Server CE databases on PDAs synchronising with it, can I get away with no licensing cost if I use the SQL Server Express Edition?
2) SQL Server <> SQL Server (Mobile Application Database) <> SQL CE
If we then complicate the model as the mobile application main SQL Server database has a service runninhg which then synchronises via .NET and web services to another database that is SQL Server based, does this cause problems with licensing, e.g. in the area of multiplexing because we know our ultimate end PDA users?
3) Oracle <> SQL Server (Mobile Application Database) <> SQL CE
How would licensing be affected if the backend system is changed to Oracle.
Thanks.
SQL Express Edition is free to use - it's got it's limitations but if your app can work inside it's constraints then it's fine to use.
You're not clear on point 2 but if all of those SQL installations are Express or CE/Compact then that's fine as well.
You license costs would come in if you put a Standard/Enterprise edition SQL Server in the mix at which point you either need to look at CAL licensing or get Proc license(s).
If SQL Express will meet your needs then there shouldn't be any licensing issues.
If you use a version of SQL that requires licensing you have to get CAL's for your known users, or go the per-CPU licensing route which doesn't require CAL's.
Related
I've been doing this for 3 days. I couldn't find the solution. Normally it was supposed to have features like the following.
What is the cause of this problem? And how do I solve it?
You're using SQL Server Express. SQL Server Express is a very cut down version of SQL Server and does not provide anywhere near as many features as Standard and Enterprise; such as database mail (Additional Database Services). If you need features, you need to purchase SQL Server and pay for the edition licences that have the features you need.
If you are using SQL Server for development purposes only, you can use SQL Server Developer Edition, which is allowed to be used for non-production environments only. Developer edition has all of the features that Enterprise does.
You can find the full list of features supplied by each edition here: Editions and supported features of SQL Server 2017
When a project is created in Asp.net MVC you have the possibility to choose between different types of database, which is the recommended and what are their differences and uses.
SQL Server runs as a service, whereas SQL Server Compact is an embedded database in the same physical location as the application. SQL Server Compact is meant for a standalone application and is not intended to be shared among many users or in situations where there is a lot of concurrent access, such as with a web site.
SQL Server runs as a service and listens for requests on a port. You can have multiple concurrent connections with its use and it acts as a gatekeeper checking for permissions from incoming connections. It is meant for work groups and enterprises, and is not intended (overkill) for single-user/single-computer applications.
SQL Server Express is the free edition of the full SQL Server, and has certain limitations such as a maximum database size of 10GB, among others. SQL Server Standard is like the full edition. There are also Enterprise, Datacenter, and Developer editions.
I just wrote a large program using SQL Server Express and was very happy, the difficulty is that it is difficult for customers to install SQL Server to test the program out.
I looked into SQL Server CE and it looks great for smaller clients and trial software. However SQL Server CE uses System.Data.SqlCeServer and not System.Data.SqlClient
Is there a way to make an application that uses SQL Server CE and then if desired the client can upgrade to SQL Server Express?
No, they're different platforms. CE is for the Compact Edition, so it's intended to be used on sometimes disconnected devices with limited resources compared to a SQL Server. CE should have a subset of Express' functions.
Very new to SQL Server. I am needing to develop a SQL Server database to run with an iPhone app I am developing. It will ultimately be running with our full-fledged SQL Server database, which is administered by our IT guy, but I'd like to have a local database for testing.
Two questions:
I assume I can use SQL Server Express 2012 for this purpose, since it is advertised as such; but would it be better/easier to use what appears to be the simplest form, LocalDB, in conjunction with VB2010? It will be running on my office PC to which a port is open for TCP communication from my app (which is working fine). Would LocalDB work for that, if the communication occurs in the VB app? Or will I need to get the SQL Server Express edition?
If a prototype database is developed in SQL Server Express, can it migrate to our full-fledged SQL Server when the app is taken "live"? (I am not sure right now what version our full-fledged SQL Server is, but I was planning on using SQL Server Express 2012.)
Yes, the Express editions ARE the full-fledged SQL Server version - no code difference, only some marketing-driven restrictions (on database size and so forth).
You can absolutely develop your system on a SQL Server Express, and then just detach your database from Express and re-attach it to a Standard or Enterprise edition server. No fuss, no migration, no conversion - nothing - it just works. Period.
And I would probably even argue having a server installation (of your Express) edition is the better choice than LocalDB. That way, you're already using the server-based approach as you will later on in production, and you won't fall into any "convenience" traps offered by LocalDB (or other approaches) that make dev life easier - but rollout to production can be a challenge. When you use SQL Server Express as a server-based installation from the get to - you have the "real deal" from day one.
I was wondering if we could backup the database that we currently host on regular SQL Server, and put it onto our clients computer when we setup SQL Server Express for them.
Is this possible?
Thanks,
Matt
Yes, it's possible to restore a database backup from the Standard edition to the Express edition. It's not possible to restore a SQL Server 2008 to a SQL Server 2005 version, though.
However, there a some minor differences between versions. I've noticed an issue in SQL Server Express 2005 when calling .NET SQL CLR functions across databases, so your mileage may vary. I haven't been able to find a good overview of the exact differences between the various SQL Server editions.
It's always best to keep the development platform as close as possible to the release platform. I can only recommend that you use the Express edition of SQL Server for development as well; and re-test your application.