MSDN Webcast: Introducing SQL Server Compact 3.5

re: MSDN Webcast: Introducing SQL Server Compact 3.5

Matt Adamson — Sun, 07 Dec 2008 22:19:20 GMT

Hi Steve,

I also get the same issue from the exception

$exception {"Attempted to read or write protected memory. This is often an indication that other memory is corrupt."} System.Exception {System.AccessViolationException}

My call stack looks like

[Managed to Native Transition]

> System.Data.SqlServerCe.dll!System.Data.SqlServerCe.SqlCeCommand.ReleaseNativeInterfaces() + 0x23 bytes

System.Data.SqlServerCe.dll!System.Data.SqlServerCe.SqlCeCommand.Finalize() + 0x23 bytes

We use a LINQ to SQL data context however we always ensure a new context is created for each. It's actually used through windows workflow foundation and currently we've had to use the manual thread scheduling service due to this issue when the default service is used. As you probably know the default service schedules work using the CLR thread pool.

I could certainly capture and upload a dump file when this exception occurs if it would help diagnose the issue?

re: MSDN Webcast: Introducing SQL Server Compact 3.5

Steve Lasker -MS — Thu, 20 Nov 2008 07:06:07 GMT

Hi Dilip,

I'm afraid we'll need a bit more info to understand why you're getting the error. Are you saying it works for the first "thread", but not the other? Are you attempting to use the same connection across different threads? If so, that would be a problem. Connections aren't thread safe. You can open multiple connections from different threads or different processes against the same database. You can even pass a connection from one thread to another to maintain a collection of open connections, for perf. You just can't use the same connection, at the same time, from two different threads.

Steve

re: MSDN Webcast: Introducing SQL Server Compact 3.5

dilip kumar — Mon, 17 Nov 2008 20:05:45 GMT

hi,

i am getting exception

“Attempted to read or write protected memory. This is often an indication that other memory is corrupt.” when try to acces SQL ce 3.5 DB in Multithread environment.

Please provde me the solution.

Thannks,

Dilip

re: MSDN Webcast: Introducing SQL Server Compact 3.5

Steve Lasker -MS — Tue, 13 May 2008 21:23:43 GMT

Hi Leon,

The SP1 Beta of Visual Studio 2008 and SQL Server Compact is available here. When you install Visual Studio SP1, you�ll get Compact SP1 as well. However, this unfortunately doesn�t include the beta of our 64bit release. Since this didn�t ship �in VS 2008�, it doesn�t get included with the SP.

The official statement for SP1 release is �this summer�, which is when we�ll be releasing the 64bit bit release as well. If you�d like to contact me directly, we can see if we can help you in the shorter term if this doesn�t meet your schedule needs.

re: MSDN Webcast: Introducing SQL Server Compact 3.5

Leon — Tue, 13 May 2008 21:15:08 GMT

Do you know approximately know in how soon the beta is going to released?

re: MSDN Webcast: Introducing SQL Server Compact 3.5

Steve Lasker -MS — Sun, 11 May 2008 19:53:00 GMT

Hi Lee,

Yes, we absolutely do have a 64bit release coming. With the popularity of private deployment, we had a few extra challenges we wanted to get right before releasing it, so it’s coming in our SP1 release. I’ll be posting more info when I have dates I can tell customers when they can get a download of a beta.

Steve

re: MSDN Webcast: Introducing SQL Server Compact 3.5

Lee — Wed, 07 May 2008 17:32:48 GMT

Steve,

The "Choosing Between SQL Server 2005 Compact Edition and SQL Server 2005 Express Edition" whitepaper you wrote in 11/2006 stated that 3.5 would support native x64 (or more accurately, the next version after 3.1). I believe that 3.5 still needs WoW. Are there any plans to support native 64-bit with CE?

Lee

re: MSDN Webcast: Introducing SQL Server Compact 3.5

Steve Lasker -MS — Sun, 30 Mar 2008 02:15:31 GMT

Hi,

Yes, you can open connections from multiple threads and processes on the same machine, and this is fully supported. We use shared memory to map connections between multiple processes.

The thing we stop at is supporting multiple connections from remote machines. We really don’t want to re-create the Jet problem where people can get a few connections to a network share, and then things just start getting ugly. As files continue to grow, it’s just not practical to manage a data file across the network. You could of course, write a service to front Compact so you get true client/server behavior, but Compact isn’t tuned for thrashing of hundreds of concurrent connections. If you need multiple connections from the network, this is really where Express is a great place to start.

However, for your initial question, yes, this is fully supported.

Steve

re: MSDN Webcast: Introducing SQL Server Compact 3.5

gdc — Sat, 22 Mar 2008 12:50:01 GMT

Hi Steve,

your presentation was really interesting.

I supposed that SQL Server Compact was only for single application (single process) access, but in your sample you share the same northwind.sdf file with two applications (both with open connections on the file).

Is this a supported scenario?

Thank you

re: MSDN Webcast: Introducing SQL Server Compact 3.5

Scott — Tue, 04 Mar 2008 22:39:33 GMT

Steve,

Thanks for your help. An Upsizing wizard would be very helpful in this scenario. I ended up using Primeworks Data Port Wizard to move the data and schema to SQL express then I created a LocalDataCache. Sync now works great. Very cool!

Scott