We have upgraded to PDM 2021 and solidworks 2021. to do this we had to move to a new server with the new version of server OS we also have the newest version of SQL Server installed.
The issue we are having is 2 fold. all check-ins are painfully slow, I'm talking 15 minutes for medium to small-sized assemblies. Some of this maybe Server priority allocation and we are dealing with that.
The bigger issue that I really need to be solved is that we can not check in a drawing with a BOM in it. I have tried BOM templates that are default with install and it has the same issue. Tables and cultists work fine, BOM table and it just won't check in. Delete the BOM and it checks in fine. We are completely stuck as all of our drawings have a BOM.
here is the server report of what is hanging:
(
Select top 1 1
From UserProjectRights upr
Where upr.ProjectID = @iProjectID
And upr.UserID = @iUserID
And (Type & @iPerm) = @iPerm
)
Or
Exists
(
Select top 1 1
From GroupProjectRights gpr
Join dbo.GAS_fnProjectGroupMembersForUser(@iUserID, @iProjectID) gm
On gm.ProjectID = gpr.ProjectID
And gm.IsMember = 1
And gpr.GroupID = gm.GroupID
Where gpr.ProjectID = @iProjectID
And (Type & @iPerm) = @iPerm
)
Hi Josh,
the behavior with check in hanging on drawings with a BOM table may be related to the following SQL 2019 specific bug:
SPR 1200002 "Check in of drawing containing a SW CAD BOM hangs and cause 100% CPU (on 'SPU_UndoLockFile') when using SQL Server 2019 compatibility level (150) *SWPDM 2021 specific*"
If you upgrade to SOLIDWORKS PDM 2021 on a Microsoft SQL Server 2019 server - the vault database will automatically be set to the SQL 2019 compatibility level (150). Refer to knowledge base solution S-077807. This allows the SQL engine to try to use the SQL 2019 optimized query engine. Unfortunately, at times, the newer query engine may cause the SQL queries used by SOLIDWORKS PDM to not run as optimal as it should. With this SPR, we've seen that check in could hang in certain vaults if the database is set to compatibility level 150.
As a first step, I would suggest that you lower the compatibility level to 140 instead and see if the check in works better (open SQL Management Studio, right-click the vault database, Properties, Options). Level 140 makes the queries run with the SQL 2017 engine instead and this issue is not observed there.
We have made correction to this in the upcoming 2021 SP3 release.
Hope this helps, if not, please report this problem to your VAR for further troubleshooting with SW Technical Support.
Regards -Tor