It is on MSDN subscriber downloads!!
-
-
English downloads are available now and additional languages will be added on a daily basis. Visual Studio 2008 users will need to download and install Service Pack 1 which will be available on MSDN after August 11, 2008.
-
jh71283
Throw new System.Beverage. OutOfCoffeeException()
SQL Server 2008 Express will be available for download at the end of August 2008.gadget said:English downloads are available now and additional languages will be added on a daily basis. Visual Studio 2008 users will need to download and install Service Pack 1 which will be available on MSDN after August 11, 2008.
Typical.
-
jh71283
Throw new System.Beverage. OutOfCoffeeException()
Well at least they are effectively giving a provisional date of Aug 11th for SP1... but I notice that it will be available for download 'After' August 11th.... yeah well technically so is christmas...
-
jh71283
Throw new System.Beverage. OutOfCoffeeException()
hah...I'm such a post * (Whoops swear filter... it rhymes with more.)...
It seems thay have messed up the docs...
If you look at the SQL 2008 Express vs Compact comparison, It seems OK. However if you Review the detailed feature Comparison (PDF) at the bottom, it implied that Compact is more capable than Express! -
Cool. That is a pain about about needed sp1 if you have vs2008 another week to wait! So erm what happens if you dont have sp1 does it not let you install?jh71283 said:hah...I'm such a post * (Whoops swear filter... it rhymes with more.)...
It seems thay have messed up the docs...
If you look at the SQL 2008 Express vs Compact comparison, It seems OK. However if you Review the detailed feature Comparison (PDF) at the bottom, it implied that Compact is more capable than Express!
-
jh71283
Throw new System.Beverage. OutOfCoffeeException()
Well I assume it will install, but the tools in VS may not work correctly against 2008.alexmac said:
Cool. That is a pain about about needed sp1 if you have vs2008 another week to wait! So erm what happens if you dont have sp1 does it not let you install?jh71283 said:*snip*
-
jh71283 said:
Well I assume it will install, but the tools in VS may not work correctly against 2008.alexmac said:*snip*
Hmm might wait as dont want it to stop vs2008 working or anything.
Do you know if it is possible to install sql 2008 alongside 2005? -
jh71283
Throw new System.Beverage. OutOfCoffeeException()
I think you probably could, providing you install it as a different instance name.alexmac said:jh71283 said:*snip*Hmm might wait as dont want it to stop vs2008 working or anything.
Do you know if it is possible to install sql 2008 alongside 2005?
When in doubt, use virtual PC to try it out....
-
wisemx
Live it
I'm running 2005 and 2008 on the same Vista box with no issues.alexmac said:jh71283 said:*snip*Hmm might wait as dont want it to stop vs2008 working or anything.
Do you know if it is possible to install sql 2008 alongside 2005? -
boondox
Just Because...
Is SP1 only needed for SQL 2008 Express or the entire line of SQL 2008 products?gadget said:English downloads are available now and additional languages will be added on a daily basis. Visual Studio 2008 users will need to download and install Service Pack 1 which will be available on MSDN after August 11, 2008.
-
If you want SQL 2008 support in visual studio 2008 you need sp1.boondox said:
Is SP1 only needed for SQL 2008 Express or the entire line of SQL 2008 products?gadget said:*snip*
-
staceyw
Before C# there was darkness...
-
Maybe you are thinking of something else, but it only looks that way from a programmability and deployment standpoint. It's because Compact is only just a handfull of assemblies that you reference in your project, it's stupid simple to deploy. Running in process also opens it up to a lot more flexibility for certain scenarios than having a server instance that's locked to a single machine.jh71283 said:hah...I'm such a post * (Whoops swear filter... it rhymes with more.)...
It seems thay have messed up the docs...
If you look at the SQL 2008 Express vs Compact comparison, It seems OK. However if you Review the detailed feature Comparison (PDF) at the bottom, it implied that Compact is more capable than Express!
Obviously, it comes with limitations. It's not a server in the sense that it can't serve data to other machines. If you just need a local data store, then it's pretty good. We use it for enabling occasionally-connected scenarios where data gets synced between the local datastore and the main SQL Server. The local apps only are aware of the local database, and the data access layer handles the synchronization when it has a connection. It's great because we can use the same data access framework across all of our Windows apps, and mobile apps with zero modifications between platforms. The performance is pretty darn good too. -
blowdart
Peek-a-boo
kettch said:
Maybe you are thinking of something else, but it only looks that way from a programmability and deployment standpoint. It's because Compact is only just a handfull of assemblies that you reference in your project, it's stupid simple to deploy. Running in process also opens it up to a lot more flexibility for certain scenarios than having a server instance that's locked to a single machine.jh71283 said:*snip*
Obviously, it comes with limitations. It's not a server in the sense that it can't serve data to other machines. If you just need a local data store, then it's pretty good. We use it for enabling occasionally-connected scenarios where data gets synced between the local datastore and the main SQL Server. The local apps only are aware of the local database, and the data access layer handles the synchronization when it has a connection. It's great because we can use the same data access framework across all of our Windows apps, and mobile apps with zero modifications between platforms. The performance is pretty darn good too.Now where's VS 2008 SP1? Kind lost without VS support *grin*
Oops didn't see that - 11th? Pah!
-
The bad thing about the compact version is that you can't use parameters in your sql calls.kettch said:
Maybe you are thinking of something else, but it only looks that way from a programmability and deployment standpoint. It's because Compact is only just a handfull of assemblies that you reference in your project, it's stupid simple to deploy. Running in process also opens it up to a lot more flexibility for certain scenarios than having a server instance that's locked to a single machine.jh71283 said:*snip*
Obviously, it comes with limitations. It's not a server in the sense that it can't serve data to other machines. If you just need a local data store, then it's pretty good. We use it for enabling occasionally-connected scenarios where data gets synced between the local datastore and the main SQL Server. The local apps only are aware of the local database, and the data access layer handles the synchronization when it has a connection. It's great because we can use the same data access framework across all of our Windows apps, and mobile apps with zero modifications between platforms. The performance is pretty darn good too. -
Maddus Mattus
Do, or do not. There is no try. - Yoda
I dont think that is entirely accurate.gadget said:
The bad thing about the compact version is that you can't use parameters in your sql calls.kettch said:*snip*
I've used the compact edition and only limit I came across was not being able to use sub-queries.
edit;
http://msdn.microsoft.com/en-us/library/system.data.sqlserverce.sqlcecommand.parameters.aspx -
Maddus Mattus
Do, or do not. There is no try. - Yoda
I love the compact edition, certainly for lightweight and light footprint.jh71283 said:hah...I'm such a post * (Whoops swear filter... it rhymes with more.)...
It seems thay have messed up the docs...
If you look at the SQL 2008 Express vs Compact comparison, It seems OK. However if you Review the detailed feature Comparison (PDF) at the bottom, it implied that Compact is more capable than Express!
Only downside is not being able to use WHERE ChidID IN (SELECT ID FROM ChildTable)
Thread Closed
This thread is kinda stale and has been closed but if you'd like to continue the conversation, please create a new thread in our Forums,
or Contact Us and let us know.