Change SPROC not detected as an uncommitted Change

A SQL Server Management Studio add-in to source control your database in Subversion or Team Foundation Server.

Moderators: Chris Auckland, David Atkinson, sherr, PhilScrace, andy.campbell.smith

Change SPROC not detected as an uncommitted Change

Postby flyer299 » Fri Mar 01, 2013 10:39 pm

From time to time, I refresh my Development Database from a backup from live. This is pretty normal procedure. But I think the problem I am having has something to do with that.

When I refresh the Database, I normally unlink my DB from SQL Source and relink it, because it clear's SQL Sources Memory. So I did that this time.. (More than once now!)

I modified a PROC after the refresh. The changes will not show up on the Committ tab! No matter what I do!
flyer299
 
Posts: 6
Joined: Mon Apr 12, 2010 2:52 pm

Postby chriskelly » Mon Mar 04, 2013 3:38 pm

Just to clarify, the steps that you are following are:

- unlink dev database from repository
- restore prod database backup
- relink new dev database to repository
- change sproc and attempt to commit change

Before you make any changes are you checking whether you are on the head revision using 'Get Latest'? Is the tool picking up the revision number allowing 'Get Latest' to work? When you complete the change is the little blue blob appearing in SSMS before you go to 'Commit'?
Chris Kelly
Technical Support Engineer
chriskelly
 
Posts: 330
Joined: Mon Apr 19, 2010 1:44 pm
Location: Cambridge, UK

Postby flyer299 » Mon Mar 04, 2013 6:06 pm

Close...
- Restore Prod DB
- Unlink from SQL Source
- Link from SQL Source
- Change Sproc
- Attempt to Commit Changes

Before I make a change, I check "Get Latest" and I am all up to date.

I do not recall seeing the blue blob. But I stopped paying attention to those long ago.
flyer299
 
Posts: 6
Joined: Mon Apr 12, 2010 2:52 pm


Return to SQL Source Control 3

Who is online

Users browsing this forum: No registered users and 0 guests