Comments
Sort by recent activity
This isn't an issue we particularly see - so you're right, it's likely to be specific to your environment.
SSMS loads addins from this location:
C:\ProgramData\Microsoft\SQL Server Management Studio\12.0\Addins
(the folder may be 11.0 if you have SSMS 2008 instead)- so the first thing I'd do is ensure your standard user account has full control to that location (as it's the shared programdata location, rather than the one in your profile).
Other things to check permissions on would be:
C:\ProgramData\Red Gate\Licenses
(in the registry:) HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Red Gate\Licensing
Both of these locations will have information written to that relates to the product activation. / comments
This isn't an issue we particularly see - so you're right, it's likely to be specific to your environment.
SSMS loads addins from this location:
C:\ProgramData\Microsoft\SQL Server Management Studi...
I tried this myself a couple of years ago when another user enquired about it, but I was unable to make it work unfortunately.
I've not heard of anyone successfully coming up with a config file for it, but hopefully they will post back here if so! / comments
I tried this myself a couple of years ago when another user enquired about it, but I was unable to make it work unfortunately.
I've not heard of anyone successfully coming up with a config file for...
I've replied directly to you to get some more information. / comments
I've replied directly to you to get some more information.
Are you running the command-line under the same user account as SQL Source Control was used with? Because the LinkedDatabase.xml is in your user profile, running the commandline as a different account may result in this error as it's not able to find that file.
The other option would be to save the two extended property xml fragments out to two files (call them db.xml and mig.xml). Then add to your command-line the switches:
/sourcecontrol1 /scriptsfolderxml:<path to db.xml> /migrationsfolder:<path to mig.xml>
and remove the /server1 and /database1 switches / comments
Are you running the command-line under the same user account as SQL Source Control was used with? Because the LinkedDatabase.xml is in your user profile, running the commandline as a different acco...
It'll just get processed internally by the engine a different way. The xml files are a slightly 'older' method, originally introduced in early version 10 releases of Compare. / comments
It'll just get processed internally by the engine a different way. The xml files are a slightly 'older' method, originally introduced in early version 10 releases of Compare.
It's definitely one possible cause- there's currently a couple of possibilities we'll be investigating shortly:
- new object in the repository, but amended after it's created before it's committed (which is what you're seeing in this example)
- existing object in the repository that is dropped and recreated in the DB
- trace file has rolled over before the polling query runs.
We're hoping to work on all these fairly soon, so things should improve. / comments
It's definitely one possible cause- there's currently a couple of possibilities we'll be investigating shortly:
- new object in the repository, but amended after it's created before it's committed ...
Thanks- I've reproduced this behaviour myself (it doesn't even need two users, I made all the changes under my own user and the same 'unknown' appears)
Looks like a bug of some sort, so I'll get that logged. Hopefully we can resolve it. / comments
Thanks- I've reproduced this behaviour myself (it doesn't even need two users, I made all the changes under my own user and the same 'unknown' appears)
Looks like a bug of some sort, so I'll get th...
Thanks for those steps. In the scenario you describe, I'd expect it to show UserB against the table on the final refresh, as they made the most recent change.
Do you know if the change UserB made caused the table to be rebuilt? / comments
Thanks for those steps. In the scenario you describe, I'd expect it to show UserB against the table on the final refresh, as they made the most recent change.
Do you know if the change UserB made c...
The bottom of the page that tells you how to set those up displays a list of change types that we cannot track- is it possible those account for a lot of the missing entries?
There's also an issue (or at least *was*) where table changes made using the designer, rather than T-SQL, weren't picked up.
Also ensure all users have made the same config file change, otherwise it might be that for many users the changes are still using the old method. / comments
The bottom of the page that tells you how to set those up displays a list of change types that we cannot track- is it possible those account for a lot of the missing entries?
There's also an issue ...
If you're seeing 'unknown' a lot, try the option to log changes to a separate database. If you don't do that, it relies on reading them from the default trace and on a busy-ish server (or with lots of users) the trace file can roll over in a matter of a few minutes. This means that the information gets lost quite quickly / comments
If you're seeing 'unknown' a lot, try the option to log changes to a separate database. If you don't do that, it relies on reading them from the default trace and on a busy-ish server (or with lots...