Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
DB Engine
SQL ServerMSDESQL Server CE
Services
Analysis (Data Mining)Analysis (OLAP)DTSIntegration ServicesNotification ServicesReporting Services
Programming
CLRConnectivitySQLXML
Other Technologies
ClusteringEnglish QueryFull-Text SearchReplicationService Broker
General
Data WarehousingPerformanceSecuritySetupSQL Server ToolsOther SQL Server Topics
DirectoryUser Groups
Related Topics
MS AccessOther DB ProductsMS Server Products.NET DevelopmentVB DevelopmentJava DevelopmentMore Topics ...

SQL Server Forum / DB Engine / SQL Server CE / December 2008

Tip: Looking for answers? Try searching our database.

Sql Compact 3.1  desktop and Sql Compact 3.5 desktop on the same PC

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Thore Berntsen - 26 Nov 2008 20:26 GMT
Can Sql Compact  3.1 desktop and Sql Compact 3.5 desktop live side by side
the same PC?

Thore Berntsen
Laxmi Narsimha Rao Oruganti [MSFT] - 27 Nov 2008 05:41 GMT
Yes.  Yes. Yes.   Both are SxS installations and do not interfere in each
others business

Thanks,
Laxmi

> Can Sql Compact  3.1 desktop and Sql Compact 3.5 desktop live side by side
> the same PC?
>
> Thore Berntsen
Michael Barrett - 30 Nov 2008 14:36 GMT
> Yes.  Yes. Yes.   Both are SxS installations and do not interfere in each
> others business

How do you determine which one you are using if you design a new database?

For example, say you use SQL Express to create an SDF file. It always seems
to default to 3.0. How do you create a 3.5 sdf?
Laxmi Narsimha Rao Oruganti [MSFT] - 01 Dec 2008 04:23 GMT
Ok few clarifications to avoid confusion with SKUs.

1) SQL Express is not same as SQL Compact.  SQL Express is a stripped down version of SQL "big" Server and runs as a service have instances concept
2) SQL Compact (or SQL CE) is an embedded and in-proc database, and runs in applications process
3) SQL CE 3.0 and SQL CE 3.1 are not SxS
4) SQL CE 3.0/3.1 and SQL CE 3.5 are SxS

Now assuming that you application is written in C#:
1) If you have compiled your application executable with a reference to SQL CE 3.0 Provider DLL; then it always creates a 3.0/3.1 database
2) If you have compiled your application executable with a reference to SQL CE 3.5 Provider DLL; then it always creates a 3.5 database

I know this looks totally different from what other "big" servers do as they go with client-server model.  Where as SQL CE (like any other embedded database engine) is pretty much tightly coupled with applications and hence the way you reference is what determines which engine to load.

If your application is written in C++ (native) and using OLEDB programming model:
SQL CE CLSIDs and ProgIDs are version dependant.  So, check the engine you are referring to in your code.

Thanks,
Laxmi

>> Yes.  Yes. Yes.   Both are SxS installations and do not interfere in each
>> others business
[quoted text clipped - 3 lines]
> For example, say you use SQL Express to create an SDF file. It always seems
> to default to 3.0. How do you create a 3.5 sdf?
Michael Barrett - 01 Dec 2008 14:53 GMT
Thank you. I am aware of the differences between Compact and Express. However, you can use SQL Express to create and manage .SDF files.

I have SQL Server Express 2005 and VS.Net 2005 installed. I typically use VB.Net. I am new to .SDF development and am just finding my way around now. I planned on using the SQL Server Mgmt Studio GUI to maintain the SDF, then update it in the application by refreshing the imported DataSet object.

QUESTION: Lets say I created the db in C:\MySDF\ then import the object. It recreates the file in the application directory. If I continue to edit the file in C:\MySDF, how do I reflect those changes in the imported DataSet? Is there a simple way to replicate? What is the best practice here? Am I forced to use the DataSet designer in VB.Net?

Thanks,
Mike
 Ok few clarifications to avoid confusion with SKUs.

 1) SQL Express is not same as SQL Compact.  SQL Express is a stripped down version of SQL "big" Server and runs as a service have instances concept
 2) SQL Compact (or SQL CE) is an embedded and in-proc database, and runs in applications process
 3) SQL CE 3.0 and SQL CE 3.1 are not SxS
 4) SQL CE 3.0/3.1 and SQL CE 3.5 are SxS

 Now assuming that you application is written in C#:
 1) If you have compiled your application executable with a reference to SQL CE 3.0 Provider DLL; then it always creates a 3.0/3.1 database
 2) If you have compiled your application executable with a reference to SQL CE 3.5 Provider DLL; then it always creates a 3.5 database

 I know this looks totally different from what other "big" servers do as they go with client-server model.  Where as SQL CE (like any other embedded database engine) is pretty much tightly coupled with applications and hence the way you reference is what determines which engine to load.

 If your application is written in C++ (native) and using OLEDB programming model:
 SQL CE CLSIDs and ProgIDs are version dependant.  So, check the engine you are referring to in your code.

 Thanks,
 Laxmi

 "Michael Barrett" <michaelfbarrett_notthispart@yahoo.com> wrote in message news:OCCn8jvUJHA.1908@TK2MSFTNGP04.phx.gbl...
 >> Yes.  Yes. Yes.   Both are SxS installations and do not interfere in each
 >> others business
 >
 > How do you determine which one you are using if you design a new database?
 >
 > For example, say you use SQL Express to create an SDF file. It always seems
 > to default to 3.0. How do you create a 3.5 sdf?
 >
 >
Michael Barrett - 01 Dec 2008 15:08 GMT
I think I answered my own question....  I simply open the sdf file from the application location, make changes, then refresh the data connection SDF file, THEN add the new objects to the DataSet in the designer. It is awkward though because it appears I need to delete and re-add in the dataset designer if a column is added or modified.

I think I need a good book on developing SQL Server Compact with Visual Studio...  Any suggestions?

 Thank you. I am aware of the differences between Compact and Express. However, you can use SQL Express to create and manage .SDF files.

 I have SQL Server Express 2005 and VS.Net 2005 installed. I typically use VB.Net. I am new to .SDF development and am just finding my way around now. I planned on using the SQL Server Mgmt Studio GUI to maintain the SDF, then update it in the application by refreshing the imported DataSet object.

 QUESTION: Lets say I created the db in C:\MySDF\ then import the object. It recreates the file in the application directory. If I continue to edit the file in C:\MySDF, how do I reflect those changes in the imported DataSet? Is there a simple way to replicate? What is the best practice here? Am I forced to use the DataSet designer in VB.Net?

 Thanks,
 Mike
Laxmi Narsimha Rao Oruganti [MSFT] - 02 Dec 2008 11:10 GMT
A consolidated information blog (points out the books):
http://blogs.msdn.com/stevelasker/archive/2008/11/25/demos-presentations-links-s
creencasts-and-videos-for-sql-server-compact.aspx


Thanks,
Laxmi
 I think I answered my own question....  I simply open the sdf file from the application location, make changes, then refresh the data connection SDF file, THEN add the new objects to the DataSet in the designer. It is awkward though because it appears I need to delete and re-add in the dataset designer if a column is added or modified.

 I think I need a good book on developing SQL Server Compact with Visual Studio...  Any suggestions?

   "Michael Barrett" <michaelfbarrett_notthispart@yahoo.com> wrote in message news:uyhbcS8UJHA.1164@TK2MSFTNGP02.phx.gbl...
   Thank you. I am aware of the differences between Compact and Express. However, you can use SQL Express to create and manage .SDF files.

   I have SQL Server Express 2005 and VS.Net 2005 installed. I typically use VB.Net. I am new to .SDF development and am just finding my way around now. I planned on using the SQL Server Mgmt Studio GUI to maintain the SDF, then update it in the application by refreshing the imported DataSet object.

   QUESTION: Lets say I created the db in C:\MySDF\ then import the object. It recreates the file in the application directory. If I continue to edit the file in C:\MySDF, how do I reflect those changes in the imported DataSet? Is there a simple way to replicate? What is the best practice here? Am I forced to use the DataSet designer in VB.Net?

   Thanks,
   Mike
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.