Activity overview
Latest activity by shaulbehr
My main db is on the MyDomain domain, and I have a user MyDomain\me.
I have a qa db on a different domain than my main TFS server. I still need to attach the DBs to the TFS source control, but I can't even run SSMS as MyDomain\me because the QA server doesn't recognize that domain, and I can't set up MyQADomain\meAsQA as a TFS user because MyDomain doesn't recognize that user.
So how do I forcibly override the TFS credentials? / comments
My main db is on the MyDomain domain, and I have a user MyDomain\me.
I have a qa db on a different domain than my main TFS server. I still need to attach the DBs to the TFS source control, but I c...
Can't link to source control
I have a DB under source control, 2 computers are linked to it.
I'm now trying to connect a 3rd DB. Now I am having trouble connecting.
While I am able to browse to the SVN folder, to select the f...
Yep, that was the problem.
Uninstalled and reinstalled SQL Test, now everything is working fine.
Thank you very much! / comments
Yep, that was the problem.
Uninstalled and reinstalled SQL Test, now everything is working fine.
Thank you very much!
I realized I recently upgraded my DB from SQL 2008 R2 to 2012, and thought maybe the problem is because I was still using SSMS 2008. So I opened SSMS 2012, and went through the same steps of adding a migration script. Now instead of raising that rubbish error, it crashes the whole SSMS. / comments
I realized I recently upgraded my DB from SQL 2008 R2 to 2012, and thought maybe the problem is because I was still using SSMS 2008. So I opened SSMS 2012, and went through the same steps of addin...
David Atkinson wrote:
On the second computer, does this have migrations enabled in the setup tab? It's possible that this is linked but without having specified the migrations folder.
You can check this in the setup tab as well as just clicking on the migrations tab to see if anything is listed.
David Atkinson
Red Gate
Hi David,
Thanks for pointing this out - yes, you are correct: the 2nd machine did not have the migration folder set up.
But the original problem still stands. I still cannot create any migration scripts on the first computer. Looks like it was sheer dumb luck that got it to commit that once. I just created a test table on my 1st computer, checked it in, updated on the 2nd computer. Then I added a not nullable column to the 1st computer with a migration script, and I cannot commit the script to source control. Same rubbish error as before.
There has to be a secret switch somewhere, because it's inconceivable that the product is generically defective in this area. But the fact is, I haven't done anything fancy with my installation, and out of the box, this feature does not work.
Just to be sure, I switched computers and added the migration script from Computer 2. Exactly the same stupid error.
What now? / comments
David Atkinson wrote:
On the second computer, does this have migrations enabled in the setup tab? It's possible that this is linked but without having specified the migrations folder.
You can ch...
Sheesh, the error suddenly went away, seemingly of its own accord.
The only thing that changed was, in yet another attempt to reproduce the error, I had, for the first time, *not* closed the "Migration script" window in SSMS, so when I clicked on "add a migration script", it warned me that I was about to discard my changes to the previous script. I said fine, discard, it regenerated the script, I pasted my script back into the window, clicked "Proceed to commit", and this time, instead of getting me to save the script file, it proceeded back to the "Commit Changes" panel, with my new migration script now listed in the changes to be committed.
But a new problem has now arisen: I checked in my changes, but on another computer, when getting latest, the migration script is nowhere to be found. So it tries to add the not null column with a default script, which of course fails.
Where did my migration script go?? / comments
Sheesh, the error suddenly went away, seemingly of its own accord.
The only thing that changed was, in yet another attempt to reproduce the error, I had, for the first time, *not* closed the "Migra...
URGENT: Nonsense error when saving migration script
I've made a change to a table that added a non-null column. SQL Source Control correctly determined that this change should need a migration script.
So I click the "Add a migration script" link, w...