Answers to Embedded Database webcast

  • Article

Asked: Can you, i.e. is it legal, to sell a product that includes the free

SQL Express dB???

 

Answered: Absolutely, SQL Express is free to download, free to use and free to deploy, you can even sell your application that includes SQL Express. We do ask that you register for redistribution at https://www.microsoft.com/sql/editions/express/redistregister.mspx.

 

 

Asked: Can you discuss some scenarios when one might want to consider

using SQL Mobile?

 

Answered: SQL Mobile, and it's soon to be released face-lift, SQL Everywhere is ideal for creating applications that need a light-weight , local data store that doesn't need to include programmability functionality. You also would use SQL Mobil as the data store on mobile devices, such as the Pocket PC. You can read more about SQL Everywhere by reading Steve Lasker's blog at https://blogs.msdn.com/stevelasker/.

 

 

Asked: Could the database name be encoded/include the application published version to ensure the database is never lost?

 

Answered: You could do this, but that might result in having to recompile the application if you ever do change the database name. Embedding the database directly into your application, either the "normal way" or by using resource files will actually result in your application carrying the copy of your database with it.

 

 

Asked: Are "named instances" still available with SQL Express? User instances are just an additional instance for storing true "per-user" data?

 

Answered: Yes, Named Instances are available in all Editions of SQL Server 2005, in fact, the default installation of SQL Express is to a Named Instance of SQLEXPRESS. User Instances are a special kind of SQL instance that results from starting a SQL Server process in the context of the application user. These User Instances are single user and only support local connections so only work for personal data.

 

 

Asked: Can you also talk about differences in debugging and security for these environments?

 

Answered: SQL Everywhere supports password protection and 128-bit encryptions. It has its own set of debuggers but they are considering making plug-ins available for additional debuggers in the future. Look for more information on this as the release matures.

 

 

Asked: When might one become involved in beta for SQL Everywhere?

 

Answered: The SQL Everywhere CTP will be officially announced at TechEd on June 12.

 

 

Asked: Will there be separate project types for SQL Mobile and SQL Everywhere?

 

Answered: No, SQL Everywhere replaces SQL Mobile.

 

 

Asked: What happens to the log file that normally travels with the mdf?

 

Answered: When VS embeds a database into the project, the log file is automatically created, you can see it by clicking the "expand" button next to the database in Project Explorer. In the solution that I showed where the mdf file is put into a Resource file, I took advantage of the fact that SQL Server will automatically generate a new log file when attaching a database provided the database was correctly closed and detached from the server where it was created.

 

 

Asked: Can SQL Express be installed along side SQL Server 2005 Enterprise Edition?

 

Answered: Yes, all Editions of SQL Server 2005 can be installed side by side provide you are within the limits on the number of instances (16 for Express and 50 for all other Editions) and you don't try to give them the same Instance Name.

 

 

Asked: Can't we use merge replication to update the target database with the changes?

 

Answered: Yes, you can use Merge replication to send changes to the target database. SQL Express only support being a subscriber in replication, so you would need one of the paid Editions to be the publisher as well as the appropriate CALs to connect to the paid Editions.

 

 

Asked: SBS2003 installs several copies of MSDE on the SBS2003 server can those MSDE instances be upgraded to SQL Express?

 

Answered: According to the SBS2003 team, upgrading from MSDE to SQL Express is not supported. I've also heard that some of the functionality in SBS2003 depends upon SQL Agent, which is not included in SQL Express. Given this, I would not recommend this upgrade.