Show history not working after upgrade to 3.1.0
Moderator: SourceGear
Show history not working after upgrade to 3.1.0
I've just upgraded to 3.1.0 and the show history by item (on a folder) doesn't work (returns no rows). The by version does work though.
Any ideas?
Any ideas?
Let's see if we can get a better picture of what is going on.
Do you have access to the database? If so, let's try this:
SELECT userid FROM sgvault.dbo.tblusers WHERE login = N'YOUR_USER_NAME_HERE'
SELECT repid, name FROM sgvault.dbo.tblrepositories
Using the userid, repid, can you run / report the results of
SELECT * FROM sgvault.dbo.ufngetusersecurityrights(REPID_HERE, USERID_HERE, DEFAULT)
If you do not want to post the results, please email me (using the button below this post), and we can take this offline.
Do you have access to the database? If so, let's try this:
SELECT userid FROM sgvault.dbo.tblusers WHERE login = N'YOUR_USER_NAME_HERE'
SELECT repid, name FROM sgvault.dbo.tblrepositories
Using the userid, repid, can you run / report the results of
SELECT * FROM sgvault.dbo.ufngetusersecurityrights(REPID_HERE, USERID_HERE, DEFAULT)
If you do not want to post the results, please email me (using the button below this post), and we can take this offline.
Jeff Clausius
SourceGear
SourceGear
Jeff,
It gives me a bunch of folders. For example, it includes the folder:
$/xx/yy
If I do a history on this folder, then it works and gives the history for the folder and all subfolders. If I do a history on a sub-folder not in this security list (eg $/xx/yy/v 2.0) then it doesn't work.
Does that help, or do you need the entire results set?
It gives me a bunch of folders. For example, it includes the folder:
$/xx/yy
If I do a history on this folder, then it works and gives the history for the folder and all subfolders. If I do a history on a sub-folder not in this security list (eg $/xx/yy/v 2.0) then it doesn't work.
Does that help, or do you need the entire results set?
Neil:
Have them contact me directly (using the email button below).
Some of the 3.1 stored procs were optimized to reduce the number of recompiles. However, this caused SQL Server to use an inefficient plan where there are > 4000 checked out items.
I'm currently working on a fix and should have something shortly.
Have them contact me directly (using the email button below).
Some of the 3.1 stored procs were optimized to reduce the number of recompiles. However, this caused SQL Server to use an inefficient plan where there are > 4000 checked out items.
I'm currently working on a fix and should have something shortly.
Jeff Clausius
SourceGear
SourceGear