SQL Server Everywhere Edition Case Studies

Blogs introduced a new communication mechanism allowing us to reach new and different customers.  I’ve had lots of comments and questions from people around the world and it’s been fun to hear the different scenarios you’ve been asking for. 
We’ll be launching SQL Server Everywhere Edition soon.  If you’ve got interesting scenarios where you’re using Everywhere Edition and would like to be featured as a possible case study, drop me a note. 


Comments (6)

  1. Mike Greenway says:

    Hi Steve
    I’m want to use WPF with a SqlEv resultSet – I’ve been all over the forums (sqlEv and WPF) and I nor anyone else can make it work. – dataset no problem, resultSet no go. I want to use this in my first product, a NEW type of computer based training.
    Thanks – love your work

  2. Steve Lasker says:

    Hi Mike,

    ResultSet does implement many of the DataBinding interfaces, but I’ll have to give this a try and figure out what’s missing.  

  3. We are using SQLEV in a Warehouse environment
    Using s Symbol PocketPC scanner we scanner the fisr rack check the Pallet on the first Level of this rack and then check the carton(s) on that pallet. Ideally all of the BarCodes should be unique but because they are not we are validating each of the bar codes (% different on the cartons) before returning a dataset.
    WE have a number of other programmes thgat are already working usimg SQLEv

    Our biggest problem was converting SQLServer to SQLEV because the Export programme does not work. Apparently it is being removed in the actual sqlev

    Can provide more details if necessary



  4. Steve Lasker says:

    Hi Mike,

    Here’s a sample that demonstrates how to use the ResultSet with WPF.

    The only slightly interesting thing we do here is set the DataContext to the resultSet and then use an empty Binding for ItemsSource in XAML. Binding is smart enough to see the IListSource and redirect it to the ItemsSource.

    It’s interesting to node that ResultSet implements IEnumerable, which also seems to work. It’s still better to do the Binding trick, because the IListSource is an IList, which is more efficient than IEnumerable.

    SqlCeConnection conn = new SqlCeConnection(@"Data Source = .Northwind.sdf");


    SqlCeCommand command = new SqlCeCommand();

    command.Connection = conn;

    command.CommandText = "SELECT EmployeeID, FirstName, LastName FROM EMPLOYEES";

    SqlCeResultSet resultSet = command.ExecuteResultSet(ResultSetOptions.Scrollable | ResultSetOptions.Updatable);

    listBox.DataContext = resultSet;

    <ListBox Name="listBox" ItemsSource="{Binding}">




           <TextBlock Text="{Binding Path=UpdatableRecord[(sys:Int32)0]}"/>

           <TextBlock Text="{Binding Path=UpdatableRecord[(sys:Int32)1]}"/>

           <TextBlock Text="{Binding Path=UpdatableRecord[(sys:Int32)2]}"/>





  5. OS says:

    We are using SQL Server everywhere inside an industrial automation product.  It fits in really well for one aspect of the system since deployment is greatly simplified.  In this model a SQLEv database is created and associated with a particular job.  One feature that we missed from SQL Server 2005 is the BeginXXX asychronous methods.  SQLEv can on average support a large number of operations per second but occasionally blocks for 0.5s to 1.0 (I assume to resize the database and perform maintenance operations).  We ended up creating our own version of the BeginXXX methods which works fine but I would definitely rather have this as part of the system.