2

Issue exporting Clarity Rand database using SQL Server

While exporting the Clarity rand database using SQL server connection, we ran into the following issues and would appreciate your support with resolving.

  1. Clarity index data base is empty
  2. The Modeltime query table is only available for some users, we need that to be available for all the users working on the models. 
  3. There are some query tables that are empty. E.g. (Diagnostic chart, User group, User group project, User group Revit user)
  4. Only some users are visible in user query tables. 
  5. Model Size is negative and unreal number is query tables.
  6. We need to produce a 'matrics over time' diagram like below.

Thank You,

Follow

1 reply

Votes Newest Oldest
1

James/Hafiz,

Feel free to open a support case with "support (at) Rand.com" if you want to dig more deeply into these items.

But my preliminary feedback would be:

1. ClarityIndex database is empty: The index database is built after you go into the Project Query / Setup page and choose which of the 245 tables you would like to Index. Have you done that step yet?

2. The ModelTime query does not show all users: Do all of the users have the Clarity Client Revit addin installed? Do they have settings that define where your Clarity server is, so that it knows where to send the data?

3. Empty Queries: Are you sure that there should be data in them? Do you have Clarity Groups defined with users? Diagnostic Charts?

4. Not All Users available in User Query tables? The "RevitUser" table refers to all users defined in Clarity - nothing beyond that. Are you saying that there are users that are defined in Clarity that do not exist in your view of that table?

5. ModelSize negative: There are some situations where you cannot reliably report a model size for a given Revit model, and in those cases we report "-1". You can exclude those specific rows in the RevitPerformance table.

6. Metrics over time: You should be able to produce a Metrics-Over-Time graph from the RevitPerformance table - as you mentioned in #5 above though, ModelSize is a bit of a "special case" metric, both that it is always listed, as well as because it is sometimes "-1", which should be ignored.

Best Regards,

Matt

Comment
Reply