Re: SQLite and SQL Server schemas

Greg (L), Tony That's it then! BIGINT IDENTITY columns for SQL Server/Azure sound like the easiest way out. I've never tried that combination before, never needed it, but that will make my EF5 generated POCOs have identical properties for both databases (I hope). I actually admire the "clarity" o

Re: SQLite and SQL Server schemas

Depending on your application it might make more sense to try to constrain the SQLite identity column to 32 bits, but if you can't do that you should be able to use a 64bit integer for the SQL Server column: CREATE TABLE [dbo].[ExampleTable] ( [ExampleId] [bigint] IDENTITY(1,1) NOT NULL,

RE: SQLite and SQL Server schemas

Hey Greg, SQL Server IDENTITY columns can be 32 bit or 64 bit. Both work ie: int or bigint. Regards, Greg Dr Greg Low 1300SQLSQL (1300 775 775) office | +61 419201410 mobile│ +61 3 8676 4913 fax SQL Down Under | Web: www.sqldownunder.com Fro

re: SQLite and SQL Server schemas

Are you likely to be replicating information back and forth between SQL Server and SQLite? Am currently investigating using some variation of a GUID to enable good replicability between SQL Server and SQLite when using Microsoft's open source Sync Framework 4.0 - to replace the previously used

SQLite and SQL Server schemas

Folks, I was considering being able to swap SQLite and SQL Server/Compact/Azure as the backend of my app. I use POCOs as the entities and I can generate multiple EDXMs for the databases and load them dynamically a runtime. It's a bit tricky to keep everything "neutral" and abstract the database awa