Showing posts with label compact. Show all posts
Showing posts with label compact. Show all posts

Wednesday, March 7, 2012

CLR and SQL 2005 Compact Edition

I believe that there is a also a new SQL database for the PDA. Am I right? Is it also possible to use (CF) .Net code inside this edition?

Yes. It's called SQL Server 2005 Mobile Edition. This works on Windows Mobile devices (PocketPC and SmartPhone). You need to install .NETCF 2.0 (compact framework) on the device for using SQL Mobile.

You can develop mobile applications using Visual Studio for Devices.

SQL Mobile is part of SQL Server 2005 or Visual Studio 2005.

You can get more information here:

The SQL Mobile page on MSDN : http://msdn.microsoft.com/mobility/sqlmobile/default.aspx

SQL Mobile page from SQL Server home: http://www.microsoft.com/sql/editions/sqlmobile/default.mspx

News groups: microsoft.public.sqlserver.ce. and

Msdn forums: You will find SQL Mobile under SQL Server: http://forums.microsoft.com/msdn/default.aspx?forumgroupid=19&siteid=1

|||But can you also create UDF en UDT with .Net like the desktop editions?|||SQL Mobile does not support UDT or UDF. Also the CLR is not inside SQL Mobile database. The programming model is different.

Simply stated:
SQL Mobile components is a bunch of dlls that are linked in your device application project. So the database routines are embedded in your application code.

You declare some variables, structures
Application logic - pre data processing
query, modify, delete data from SQL Mobile
Application logic - post data processing

Sunday, February 19, 2012

client side triggers?

in merge replication using sql server 2005 and sql server compact, is it possible to have triggers (or business logic) for any changes on the client side? how does a client app know an insert/update/delete has been made? also, if the article is set to download-only, can the client app also be nofied of any changes?

thanks,

bryan

Yes you can set your triggers to be FOR REPLICATION

That way they will fire when an insert,update or delete comes through replication.

Applications usually do not get notified of changes in the database by the database system. This would be possible using the CLR however normally it is the application that queries the database to see if changes have occured.

Martin