You may want to check your network and verify that your routers/switches are working correctly. EPDM depends on a reliable network connection and if there is a router or switch that is not functioning correctly, it could cause your clients to experience "slow downs" when using EPDM. It probably couldn't hurt to have your IT reset the affected networking equipment that may have been interupted by the power outage.
I have IT looking into that, but since we are on our own dedicated 1GB network, and we aren;t seeing slowdowns elsewhere, I suspect something inside EPDM. I just did a database trace on th SQL server and switching between a part model and an assembly with 12 parts causes a 12 second delay before the PDM task pane is updated. The SQL trace shows one particular event that is taking 12 seconds to complete compared to 1-10 milliseconds for everything else in the trace. The SQL for the event is:
If (object_id(N'tempdb..#InVariables') Is Not Null) Truncate Table #InVariables Else Create Table #InVariables (VarName nvarchar(260) COLLATE database_default, Idx Int)
If (object_id(N'tempdb..#InFolders') Is Not Null) Truncate Table #InFolders Else Create Table #InFolders (FolderTmpID Int, Path nvarchar(260) COLLATE database_default, FolderID Int)
If (object_id(N'tempdb..#InFiles') Is Not Null) Truncate Table #InFiles Else Create Table #InFiles (FileTmpID BigInt, FolderTmpID Int,FileName nvarchar(260) COLLATE database_default, ModTime DateTime, LocalVer Int, FileID Int,Cfg nvarchar(255) collate database_default,Cfg2 nvarchar(255) collate database_default)
SET NOCOUNT ON
Insert Into #InVariables
Select N'Description', 1
Insert Into #InFolders
Select 2, N'\engineering\library\mechanical\hardware\', -1 Union All
Select 1, N'\engineering\oracle\401xxx\', -1 Union All
Select 3, N'\engineering\oracle\404xxx\', -1 Union All
Select 5, N'\engineering\oracle\421xxx\', -1 Union All
Select 4, N'\engineering\projects\209762-palo verde small bore nozzle overlays\4. mechanical wip\', -1
Insert Into #InFiles
Select 1, 1, N'401742.sldprt', N'2012-03-12T01:36:38.000', -1, 0, N'ACTIVATED', N'@' Union All
Select 2, 1, N'401693.SLDPRT', N'2012-03-12T02:30:50.000', -1, 0, N'Default', N'@' Union All
Select 3, 2, N'UNC SHCS.SLDPRT', N'2012-09-10T13:49:12.000', -1, 0, N'0.250-20 UNC-3A 0.875 LONG', N'@' Union All
Select 4, 1, N'401788.SLDPRT', N'2012-03-12T01:36:14.000', -1, 0, N'Default', N'@' Union All
Select 5, 3, N'404812.SLDPRT', N'2012-09-24T15:02:48.000', -1, 0, N'Default', N'@' Union All
Select 6, 2, N'METRIC SHCS.SLDPRT', N'2012-09-05T18:13:16.000', -1, 0, N'M8 x 1.25 - 20mm LONG', N'@' Union All
Select 7, 4, N'MAGNET MOUNT - WAS 404811.SLDASM', N'2012-09-24T21:14:04.000', -1, 0, N'Default', N'@' Union All
Select 8, 1, N'401797.SLDPRT', N'2012-03-12T02:30:50.000', -1, 0, N'Default', N'@' Union All
Select 9, 1, N'401798.SLDASM', N'2012-03-12T02:30:50.000', -1, 0, N'Default', N'@' Union All
Select 10, 3, N'404813.SLDPRT', N'2012-03-06T19:21:52.000', -1, 0, N'Default', N'@' Union All
Select 11, 5, N'421312.SLDPRT', N'2012-09-11T15:37:56.000', -1, 0, N'Default', N'@'
Exec Doc_GetList 3, N'Description'
Pasting that into SQL Server Management Studio and debugging it shows that all the time is spent executing the Doc_GetList stored procedure. 12 seconds to return 11 rows is not what I would consider acceptable performance.
A rebuild of the database index has eliminated the problem. Execution time for the above query is now 144 milliseconds.
Glad to hear you got it worked out!
We had a similar issue related more to search performance a couple of months ago. When we first installed EPDM we paid our var to set up the SQL Server for optimal performance (their words). However... there did not put in any maintenance plans to rebuild the indexes.
The knowledge base has a summary of what to look at for slow downs (S-055284) and one reference to setting up a maintenance plan to rebuild / reorganize the indexes - which is what I followed.
Rebuilding the database index has eliminated our problem.
We experienced a similar issue. Most of our employees disabled the SolidWorks EPMD add-in, due to the decrease in performance.
I was able to get an EPDM SQL Maintenance Plan implemented, to rebuild the database index.
Here is a link to set up an EPDM SQL Maintenance Plan, which we will now be using.
Just yesterday I posted a link to an excellent book on SQL Server maintenance plans. The PDF is free to download and it describes in detail what all the maintenance tasks are and how to use them correctly. For example, reorganizing the indices is not required if you are going to rebuild the indices. Also, you typically only want to perform such tasks on user databases, not all databases.
You can find the book here:
Same problem here however the Index rebuild doesn't help. There is a 10 second delay when dragging a copy of a part from the assembly tree to the graphics area. Turn off the add-in and its instant.
Running the trace gets something similar to above. This is on 2012 sp3....I don't suppose 2013 is any better?