{"id":1294,"date":"2022-07-12T16:57:06","date_gmt":"2022-07-12T16:57:06","guid":{"rendered":"https:\/\/techpog.com\/?p=1294"},"modified":"2022-10-28T16:32:31","modified_gmt":"2022-10-28T16:32:31","slug":"saga-practice-manager-how-to-clear-locked-saga-users","status":"publish","type":"post","link":"https:\/\/techpog.com\/business-software\/saga-practice-manager-how-to-clear-locked-saga-users\/","title":{"rendered":"Saga Practice Manager – How to Clear Locked Saga Users"},"content":{"rendered":"
<\/p>\n
It would be best if you cleared all users from the database by running specific commands from Microsoft SQL Server<\/p>\n
<\/p>\n
First, everyone using Saga Practice Manager needs to save their work and log out<\/p>\n
<\/p>\n
Then you need to go to the computer\/server running Microsoft SQL Server Database<\/p>\n
<\/p>\n
Right Click RLEnterprise<\/p>\n
Click on New Query<\/p>\n
enter the command below<\/p>\n
DECLARE @sourceid varchar(100)<\/strong><\/p>\n SELECT @sourceid=SOURCE_ID FROM DATASVC_SOURCE WHERE PARENT_ID IS NULL<\/strong><\/p>\n Right Click Query then Execute<\/p>\n Once you run that command delete it and enter the command Below<\/p>\n SELECT O.PRINCIPLENAME AS ORGUNIT, U.PRINCIPLENAME AS USERNAME, P.NAME AS PRODUCT,<\/strong><\/p>\n T.* FROM DATASVC_TICKET T<\/strong><\/p>\n LEFT OUTER JOIN DATASVC_ORGUNIT_USER U ON T.ORGUSER_ID = U.ORGUSER_ID LEFT OUTER JOIN DATASVC_ORGUNIT O ON U.ORGUNIT_ID = O.ORGUNIT_ID LEFT OUTER JOIN DATASVC_SOURCE S ON<\/strong><\/p>\n T.SOURCE_ID = S.SOURCE_ID LEFT OUTER JOIN DATASVC_PRODUCT P ON S.PRODUCT_ID = P.PRODUCT_ID WHERE T.SOURCE_ID = @sourceid OR S.PARENT_ID = NULL — tracking only PM tickets. to track child modules change to S.PARENT_ID = @sourceid ORDER BY O.PRINCIPLENAME, U.PRINCIPLENAME, T.SOURCE_ID<\/strong><\/p>\n <\/p>\n Right-click query and then Execute<\/p>\n <\/p>\n Now all the users will be cleared and everyone can log back in<\/p>\n \n","protected":false},"excerpt":{"rendered":" If you are having an issue logging into Saga Practice Manager at a law office because there are too many users currently using the software this may be due to locked users. It would be best if you cleared all users from the database by running specific commands from Microsoft SQL Server First, […]<\/p>\n","protected":false},"author":2,"featured_media":2280,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[59,53],"tags":[],"yoast_head":"\n<\/h2>\n