Apparently, something in their environment caused the “Verify” process to take 5 minutes to complete. The first refresh was now as fast as SQL Server. This usually takes a few seconds and isn’t noticeable, but as a test I turned that feature off. The only other thing that I could think of that was unique to the first refresh was a setting in Crystal that does a “Verify Database” on the first refresh. ![]() I wondered if it was a data cache, but that didn’t explain why setting new parameters would be fast. I had the customer check for indexes but those had been set up to match SQL Server. Once the report was run in Oracle the first time it could be refreshed using different parameters and it would only take a few seconds. But for some reason the Oracle version would take a full 5 minutes to refresh while the SQL Server version only took a few seconds. ![]() The report was based on a command and the SQL was virtually identical. ![]() I had a customer this week who updated a report to read Oracle instead of SQL Server.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |