SQL Designer - Use? 1

[Buckaroo8]

I am unclear as to the purpose of the Crystal SQL Designer. One can create the query using SQL commands and retrieve data. Then what?
How do you reproduce your results into a report? SQL Expressions in the Field explorer is more like a OOP with SQL. Is the query designer a tool to assist with writing stored procedures?

 

[pgtek]

hi
Crystal query is like a store precedure that holds the result from your sql query.

I don't like using it because you cant link or event see it if tou have to import new tables.
you are better off using SQL query and save as a view then if you need to import a table or a view you will be able to link them.
Store procedure can not be link in crystal.

Hope this helps you

pgtek

 

[rhinok]

A lot of people don't like the SQL Designer. I think it has certain uses, however. For example, many companies have defined barriers between Report Writers and Database Developers/Admins. If you don't have access to create objects on the database (Views or Stored Procedures) you could still create powerful SQL statements using SQL Designer.

The SQL Designer is also good for writing simple queries for the sake of validation (once again,assuming you don't have access to another SQL-based tool like Query Analyzer or Toad).

 

[synapsevampire]

I urge people not to use it, and in most cases, so does Crystal Decisions.

Pgtek is mistaken, it is no more like a Stored Procedure than a Query is. It shares some common disadvantages, but do not mistake them as similar. An SP has a precompiled execution plan, and allows for very sophisticated SQL.

Since you didn't mention your Crystal version, nor your database version, the question is too generic to provide specific advice with your environment, and it would take too long to address every potential environment to assess the relative merits/disadvantages. In the future, please post specifics about your environment and intent.

In general, if you do NOT have access to the database to create Views or SP's, it can be useful to create slightly more efficient SQL than CR directly, but as a trade off, you add in a layer of potential problems, so I would reserve this for use only when all else fails.

Which for me is never.

Also if you have CR 9, you don't need it at all as you can use real SQL.

-k

 

[Ngolem]

My spin on SQL Designer is that it was more usefull in the CR 7 days. Using this tool you could compose a complex query such as employing unions which a difficult if not impossible task trying to design a report otherwise. You would then reference this SQL Design Query as the source of your report records.

You maybe able to drop such a query into CR 9.0 perhaps I don't know but you couldn't in earlier versions.

Now-a-days, use of this tool is not recommended... especially if you are web-enabling your reports

a web-enabled report doesn't recognize an SQL Designer query as a data source...so if this is your ultimate goal...do not use this tool at all.

Jim Broadbent