Which OS are you running under? I ran 2010 Betas and RCs under Vista and
Win7 without issue for months but now I'm using the RC under XP and it is
shockingly annoying. Most of the time the editor and tool windows fail to
refresh (including intellisense not showing up/what I'm typing not appearing
u
I primarily use the schema compare tools to keep all my database table,
stored procs, functions and other objects together and in source control,
but there are data generation plans and a bunch of other tools that means
you rarely need to leave the IDE. The functionality and tooling is a lot
richer
Just out of curiosity - do people really prefer this approach to managing
database schema changes?
I'd choose a migration approach every time (given the choice). Making
changes to a database and then using a tool to tell me what changes I made
just seems lame. You should know what changes you ma
The schema management tools are available in Premium and Ultimate but not
Professional. Having used the 2008 tools on a previous project I can
honestly say that its great until you need to worry about existing data (ie
Until you've deployed into production once). After that it starts to get a
littl
Do the database tools is VS2010 properly support SQLCE? VS2008
certainly doesn't. I learned long ago to just not use it. Instead I
use SQLCE Desktop Manager, generate a DB creation script and keep that
script with my VS solution. Of course, in my situation (windows
mobile) I never need to migra
Hi Folks,
We have a product comprised of desktop apps (.NET and native) that talk to
SQL Server 2008.
The database and apps get installed at client sites that we have no ongoing
control over. We use a table in the database to track schema versions and
our database creation / upgrade script uses
Good timing on this subject, as I was at a meeting this morning where we
discussed how to manage multiple databases that are slowly diverging from
each other and we have to stop this happening in a reliable way. We don't
have a dedicated DBA, just 3 developers all doing mixed tasks.
We traditio
Matt, I like to put two magic numbers in a special database table: The
change number, The compatibility number.
The first increments whenever the schema changes. The second increments only
when a "breaking" change is made.
The app startup code can use these numbers to determine if it can ru
As soon as I read 'compatibility number' in your email I remembered we
discussed this internally long ago.
Just recently I was thinking of tracking the required version for each app
that connects to the database but after thinking about it I don't think
we'll need that level of granularity. A sin
The crux of the problem is that DBMSs aren't version friendly. In fact they
aren't developer friendly.
On May 7, 2010 2:17 PM, "Greg Keogh" wrote:
Good timing on this subject, as I was at a meeting this morning where we
discussed how to manage multiple databases that are slowly diverging from
e
I have a "Version" table that has a single column, single row with a
version number in the form A.B.C.D. I started doing this to follow
the same version standard as my apps. So the number would be:
A - Breaking change
B - Non breaking change (eg additional table, additional column with default)
11 matches
Mail list logo
