How can we help you today? How can we help you today?
AdamY
The release notes say .NET Framework 4.7.2 or higher is required. I installed .NET Framework 4.8 just now but still have the SQL Prompt error. / comments
The release notes say .NET Framework 4.7.2 or higher is required. I installed .NET Framework 4.8 just now but still have the SQL Prompt error.
0 votes
The database revision changes every time changes are checked in so I don't understand how that would cause a problem. The current DB revision (in extended properties) is 11468, but I have checked in changes since the migration script check-in so it should be different. And the older migration script is still showing (10507 to 10508). I'm not doing cross-branch migration scripts. SQL Compare is seeing the "missing" migration script, too. I checked the repository locations and found this... The DB extended property "SQLSourceControl Scripts Location" shows: <?xml version="1.0" encoding="utf-16" standalone="yes"?> <ISOCCompareLocation version="1" type="TfsLocation"> <ServerUrl>https://tfs.ci.org:8143/tfs/</ServerUrl&gt; <SourceControlFolder>$/Compassion.com/Source - Database/Dev/CompassionWeb</SourceControlFolder> </ISOCCompareLocation> The DB extended property "SQLSourceControl Migration Scripts Location" shows: <?xml version="1.0" encoding="utf-16" standalone="yes"?> <ISOCCompareLocation version="1" type="TfsLocation"> <ServerUrl>https://tfs.ci.org:8143/tfs/</ServerUrl&gt; <SourceControlFolder>$/Compassion.com/Source - Database/Dev/Migration Scripts</SourceControlFolder> </ISOCCompareLocation> 'CompassionWeb 11234 to 11466.migrationScript' shows: <MigrationScript version="2" type="MigrationScript"> <Name>CompassionWeb 11234 to 11466</Name> <FromVersion version="1" type="VersionInfoRaw"> <Version>11234</Version> <ScriptFolderLocation><?xml version="1.0" encoding="utf-16" standalone="yes"?> <!----> <ISOCCompareLocation version="1" type="TfsLocation"> <ServerUrl>https://tfs.ci.org:8143/tfs/</ServerUrl&gt; <SourceControlFolder>$/Compassion.com/Source - Database/Dev/CompassionWeb</SourceControlFolder> </ISOCCompareLocation></ScriptFolderLocation> </FromVersion> <ToVersion version="1" type="VersionInfoRaw"> <Version>11466</Version> <ScriptFolderLocation><?xml version="1.0" encoding="utf-16" standalone="yes"?> <!----> <ISOCCompareLocation version="1" type="TfsLocation"> <ServerUrl>https://tfs.ci.org:8143/tfs/</ServerUrl&gt; <SourceControlFolder>$/Compassion.com/Source - Database/Dev/CompassionWeb</SourceControlFolder> </ISOCCompareLocation></ScriptFolderLocation> </ToVersion> And the migration file that is showing up properly also has the same values. "CompassionWeb 10507 to 10508.migrationScript" shows: <MigrationScript version="2" type="MigrationScript"> <Name>CompassionWeb 10507 to 10508</Name> <FromVersion version="1" type="VersionInfoRaw"> <Version>10507</Version> <ScriptFolderLocation><?xml version="1.0" encoding="utf-16" standalone="yes"?> <!----> <ISOCCompareLocation version="1" type="TfsLocation"> <ServerUrl>https://tfs.ci.org:8143/tfs/</ServerUrl&gt; <SourceControlFolder>$/Compassion.com/Source - Database/Dev/CompassionWeb</SourceControlFolder> </ISOCCompareLocation></ScriptFolderLocation> </FromVersion> <ToVersion version="1" type="VersionInfoRaw"> <Version>10508</Version> <ScriptFolderLocation><?xml version="1.0" encoding="utf-16" standalone="yes"?> <!----> <ISOCCompareLocation version="1" type="TfsLocation"> <ServerUrl>https://tfs.ci.org:8143/tfs/</ServerUrl&gt; <SourceControlFolder>$/Compassion.com/Source - Database/Dev/CompassionWeb</SourceControlFolder> </ISOCCompareLocation></ScriptFolderLocation> Does any of that help you? I'm at a loss right now. I'm considering undoing all the DB changes, then changing them back and trying it over again - but I'm a little concerned that will cause other problems. / comments
The database revision changes every time changes are checked in so I don't understand how that would cause a problem. The current DB revision (in extended properties) is 11468, but I have checked i...
0 votes
kenbroz - the answer Steve (stanori) posted has a link to a work-around solution. tSQLt is working on a permanent solution, I think. The tSQLt Google Group is very helpful and has more info, too. / comments
kenbroz - the answer Steve (stanori) posted has a link to a work-around solution. tSQLt is working on a permanent solution, I think. The tSQLt Google Group is very helpful and has more info, too.
0 votes