bbaldwin
asked on
Creating a Report Model locks up or get a Timeout message out when getting counts
When creating new Report Models in VS2005, the Report Model Wizard gets to the point where it is states that it is "Calculating column uniqueness" and it either gets locked up there or we get a message stating that the query timed out and it shows this huge query where it is counting a bunch of records from one of the tables from the Data Source View. I need to figure out how to get around this problem and move forward with creating models.
The actual error message states:
An error occurred while executing a command.
Message: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
Command:
SELECT
COUNT([Computed_DryHoleCos t]),
COUNT(DISTINCT [Computed_DryHoleCost]),
COUNT([Computed_WellworkCo st]),
COUNT(DISTINCT [Computed_WellworkCost]),
COUNT([Computed_TotalCost] ),
COUNT(DISTINCT [Computed_TotalCost]),
COUNT([Computed_Completion Cost]),
COUNT(DISTINCT [Computed_CompletionCost]) ,
COUNT([Computed_FinalDrill ingCosts]) ,
COUNT(DISTINCT [Computed_FinalDrillingCos ts]),
COUNT([Computed_FinalSuspe ndedCosts] ),
COUNT(DISTINCT [Computed_FinalSuspendedCo sts]),
COUNT([Computed_TotalActua lCosts]),
COUNT(DISTINCT [Computed_TotalActualCosts ]),
COUNT([Computed_ActualDril lingCosts] ),
COUNT(DISTINCT [Computed_ActualDrillingCo sts]),
COUNT([Computed_ActualComp letionCost s]),
COUNT(DISTINCT [Computed_ActualCompletion Costs]),
COUNT([Computed_ActualWell workCosts] ),
COUNT(DISTINCT [Computed_ActualWellworkCo sts]),
COUNT([Computed_FinalWellw orkCosts]) ,
COUNT(DISTINCT [Computed_FinalWellworkCos ts]),
COUNT([Computed_FinalCompl etionCosts ]),
COUNT(DISTINCT [Computed_FinalCompletionC osts])
FROM [dbo].[AFE] t
The actual error message states:
An error occurred while executing a command.
Message: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
Command:
SELECT
COUNT([Computed_DryHoleCos
COUNT(DISTINCT [Computed_DryHoleCost]),
COUNT([Computed_WellworkCo
COUNT(DISTINCT [Computed_WellworkCost]),
COUNT([Computed_TotalCost]
COUNT(DISTINCT [Computed_TotalCost]),
COUNT([Computed_Completion
COUNT(DISTINCT [Computed_CompletionCost])
COUNT([Computed_FinalDrill
COUNT(DISTINCT [Computed_FinalDrillingCos
COUNT([Computed_FinalSuspe
COUNT(DISTINCT [Computed_FinalSuspendedCo
COUNT([Computed_TotalActua
COUNT(DISTINCT [Computed_TotalActualCosts
COUNT([Computed_ActualDril
COUNT(DISTINCT [Computed_ActualDrillingCo
COUNT([Computed_ActualComp
COUNT(DISTINCT [Computed_ActualCompletion
COUNT([Computed_ActualWell
COUNT(DISTINCT [Computed_ActualWellworkCo
COUNT([Computed_FinalWellw
COUNT(DISTINCT [Computed_FinalWellworkCos
COUNT([Computed_FinalCompl
COUNT(DISTINCT [Computed_FinalCompletionC
FROM [dbo].[AFE] t
http://www.ironspeed.com/designer/5.0.1/webhelp/Part_VI/Timeout_expired_The_timeout_period_elapsed_prior_to_completion.htm might help
ASKER
I looked for a timeout parameter but cannot find one. Someone had suggested that it was in the Data Source but I could not find it there. When you create a Model - you just 1. Create the Data Source. 2. Create the Data Source View which is just like creating a view in SQL. and the 3. Create the Model and don't see any timeout parameters to set.
on server
In the Management Studio, from the Tools menu > select Options, then click "Designers". There is an option called "Override connection string time-out value for table designer updates:" In the "Transaction time-out after:" box, you will see the magic 30 seconds.
In the Management Studio, from the Tools menu > select Options, then click "Designers". There is an option called "Override connection string time-out value for table designer updates:" In the "Transaction time-out after:" box, you will see the magic 30 seconds.
ASKER
I found an option there in the Business Intelligence Designers (only there if you install SQL tools) and there was a timeout setting of 15. I raised it to 600 and am trying again. It takes a long timeout for the other one to timeout. I am interested to see how long this takes.
ASKER
Unfortunately, this did not help. Suggestions?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
The database does not have a log since we have it set to "Simple".
ASKER
We just started creating the models against a database with a small number of records and everything started working. I will give you the points for trying. Thanks!
ASKER
We ultimately just ran the model against a database with a small number of records and everything started to work.