Connecting to SQL Server data from within Workflow

sean_c_roberts's picture

Greetings to all!

I'm a new user, so please excuse the ignorance of my questions until I learn more.

I need to know how to get and set data from an MS SQL Server running on the same box as the Workflow server.

I've done a bit of searching and seem to have found contradictory information:

This site (http://www.incendiotechnology.com/Products/Symante...) says that there are predefined database components (much like in Delphi or other 4GL dev products - and what I'm used to):

Integrates With Most Database Technologies
Offering predefined database components that can be configured to work with a variety of databases such as DB2, Oracle, MySQL, SQL Server, Postgre SQL. Symantec Workflow supports connecting to databases via the database connectivity protocols like ODBC, thus extending the capability to handle virtually any database!

However, all the searching I've done on here and elsewhere tells me that I need to create an Integration Library in order to do this...

Which is true?

Does anyone have an samples/examples of the (hopefully) simples tasks of reading data from a SQL Server table and similarly setting data into that same SQL Server table?

Please help if you can and thanks in advance...

Sean C. Roberts
Managed Desktop Services Team Lead, AARP
Pillar Lead, Managed Desktop Center of Excellence, UNISYS
Infrastructure Architect and Technical Lead, UNISYS
sroberts@aarp.org
sean.roberts@unisys.com
sean_c_roberts@hotmail.com
work desk: (202) 434-3028
work cell: (703) 599-4770
personal cell: (703) 470-7033

rharveyva's picture

Integrations

You will need to use integrations to do the SQL stuff. I am kinda new also but I read and write to external DBs with integrations.

Bob Wooding's picture

Create Integration Components

Hi Sean, have you looked at any of the videos created by sturnbow? These offer some really good examples and should get you started. Watch all 3 videos... take care

https://www-secure.symantec.com/community/video/61...

Principal Consultant
Bob Wooding