Video Screencast Help

Query a SQL DB from CCSv11

Created: 09 May 2013 • Updated: 09 May 2013 | 6 comments

Is it possible to run a custom sql query from v11?  In 10.5.1 you could perform this query and export the results to a csv file or xls.  Can this be done in 11?

Or something similar?


Operating Systems:

Comments 6 CommentsJump to latest comment

Matt Plourde's picture

I don't think we can any more. A few things are missing in v11 (off the top of my head):

- Custom SQL query

- Renaming columns on grid output

- entering a custom text or date field into the grid

(I know I'm forgetting a few things...)

Rick_D's picture

The more I look around the more I'm seeing what you're saying.  With this said, we may very well need to keep our current 10.5.1 environment running parallel with our new v11 environment.

So in my next forum post I'll be asking if there's a way to take the data exported from 10.5.1 custom sql queries (exported to .csv backup and .xml for dashboards) and have v11 read those files and build dynamic dashboards......we are currently using tiered dashboards and they're not very easy to navigate through.

Thanks again Matt.

Matt Plourde's picture

Rick: Yeah, export your query results to SQL or CSV, and bring it back in via EDI in CCS 11. You can "correlate" the data with CCS assets and even run recon rules for anything relevant.

Rick_D's picture


I don't see that I can query within CCS to export to csv or sql so I'm guessing I have to run all my queries on a sql server, correct?  If so, I have 800+ queries to rewrite!!!!!

Rick_D's picture

.....disregard that last post.  I'm going to work on the EDI portion to get the v10.5 outputs piped into v11 somehow. 

Thanks Matt.


We do have the capability to perform custom SQL and Oracle queries in CCS 11.0, but it is now part of our EDI.

In RMS, we used the SQL and Oracle data sources to support custom SELECT statements to provide this functionality. In CCS 11.0, we expanded on that functionality by enabling more robust ODBC support through our External Data Interface. Essentially, you simply treat your database applications as if they were any other external data source, without having them tied to the database-layer constraints of the previous approach.