Showing posts with label downloaded. Show all posts
Showing posts with label downloaded. Show all posts

Friday, March 23, 2012

How to use SqlCE 3.5 with in Visual Studio 2005?

Dear All,

I have downloaded Microsoft Synchronization Services for ADO.NET CTP from:

http://www.microsoft.com/downloads/details.aspx?FamilyId=75FEF59F-1B5E-49BC-A21A-9EF4F34DE6FC&displaylang=en

This download package contains the SQL Server Compact Edition 3.5 and I have installed the same. Before that I was having SqlCE 3.1 and able to work with that fine from C# application on Desktop.

After installing the new one I could see V3.1 and V3.5 folders at: C:\Program Files\Microsoft SQL Server Compact Edition\. But when I tried to create a new data connection from Visual Studio 2005, it directly making use of V3.1.

Does anybody know how to make use of this newer version in my C# application with in Visual Studio 2005 and also enabling the same in SQL Server Management Studio?

It’s an urgent requirement for me; please do spend couple of minutes in providing the solution for this.

Thanks in advance

Hi,
Can some one help me if you have a solution for the above one|||

The development environment for SQL Server Compact 3.5 is Visual Studio 2008 Beta 1. The Beta is available for download at http://msdn2.microsoft.com/en-us/vstudio/aa700831.aspx

Visual Studio 2008 Beta 1 can be installed side-by-side with Visual Studio 2005 SP1. Visual Studio 2008 Beta 1 also installs SQL Server Compact 3.5. Prior to installing Visual Studio 2008 Beta 1 uninstall SQL Server Compact 3.5 Beta.

Regards

Ambrish

Wednesday, March 21, 2012

How to use SqlCE 3.5 with in Visual Studio 2005?

Hi,

I have downloaded Microsoft Synchronization Services for ADO.NET CTP from:

http://www.microsoft.com/downloads/details.aspx?FamilyId=75FEF59F-1B5E-49BC-A21A-9EF4F34DE6FC&displaylang=en

This download package contains the SQL Server Compact Edition 3.5 and I have installed the same. Before that I was having SqlCE 3.1 and able to work with that fine from C# application on Desktop.

After installing the new one I could see V3.1 and V3.5 folders at: C:\Program Files\Microsoft SQL Server Compact Edition\. But when I tried to create a new data connection from Visual Studio 2005, it directly making use of V3.1.

Does anybody know how to make use of this newer version in my C# application with in Visual Studio 2005 and also enabling the same in SQL Server Management Studio?

It’s an urgent requirement for me; please do spend couple of minutes in providing the solution for this.

Thanks in advance

Hi,
Can some one help me if you are aware of this situation|||

Moving to CE related forums.

Have you checked whether the newest components related services are restarted successfully.

for the VS issue you might check under VS related forums.

How to use SqlCE 3.5 with in Visual Studio 2005?

Dear All,

I have downloaded Microsoft Synchronization Services for ADO.NET CTP from:

http://www.microsoft.com/downloads/details.aspx?FamilyId=75FEF59F-1B5E-49BC-A21A-9EF4F34DE6FC&displaylang=en

This download package contains the SQL Server Compact Edition 3.5 and I have installed the same. Before that I was having SqlCE 3.1 and able to work with that fine from C# application on Desktop.

After installing the new one I could see V3.1 and V3.5 folders at: C:\Program Files\Microsoft SQL Server Compact Edition\. But when I tried to create a new data connection from Visual Studio 2005, it directly making use of V3.1.

Does anybody know how to make use of this newer version in my C# application with in Visual Studio 2005 and also enabling the same in SQL Server Management Studio?

It’s an urgent requirement for me; please do spend couple of minutes in providing the solution for this.

Thanks in advance

Hi,
Can some one help me if you have a solution for the above one|||

The development environment for SQL Server Compact 3.5 is Visual Studio 2008 Beta 1. The Beta is available for download at http://msdn2.microsoft.com/en-us/vstudio/aa700831.aspx

Visual Studio 2008 Beta 1 can be installed side-by-side with Visual Studio 2005 SP1. Visual Studio 2008 Beta 1 also installs SQL Server Compact 3.5. Prior to installing Visual Studio 2008 Beta 1 uninstall SQL Server Compact 3.5 Beta.

Regards

Ambrish

Friday, February 24, 2012

How to use both auto generated id and a guid in database

I downloaded the AdventureWorks OLTP Schema and am trying to use some of the design concepts that are used in this example but I don’t quite understand some things.

First there is a column named rowguid, at the moment I assume that this is a GUID. If this is wrong most likely my next question will make no sense.

Second if that is indeed a guid all the tables have another id; example would be Employee table would have employeeid and rowguid, why do this? My best guess is that you would use the guid to easily insert (linked/sync) data into multiple tables without needing to retrieve the id from the table that was first input into. My scenario would be inserting an employee; to insert an employee you need to create a row in the employee, contact and address tables and for ease you would use the guid to link these rows. But if this is the case wouldn’t there be sync issues that would arise?

If my guess is totally off please correct me also if anyone can direct me to some good resources that cover database design.

The schema can be downloaded at http://www.microsoft.com/downloads/details.aspx?familyid=0F6E0BCF-A1B5-4760-8D79-67970F93D5FF&displaylang=en#filelist

Thanks for any help.

The rowguid is actually used here as part of a replication example:

http://msdn2.microsoft.com/en-us/library/ms124807.aspx

Replication can add a column by this name to a schema to give it a unique value across servers. Rowguid is also a property that you can add to a guid column to tell it that it is an identifier for the row. You wouldn't generally want to have both types if you were designing a table yourself. You would just use the primary key that is set up to do the relationships and joins on.

They did this because they can use one datatype, always having a unique value across servers, no matter the table structures and type of the primary key.