December 28, 2016 at 1:42 pm
Hello,
I'm a fairly new DBA, working for a small company that just made the jump to a medium\large company. I have been asked to set up an XML Connection via web services reporting workflow and I'm wondering what needs to be installed for me to get started. I inherited a bare bones SQL Server. We do not have SSRS, Analysis services, ro IIS, installed. Integrations services is installed but it hasn't been utilized until now. What steps do I need to take to set up web services? I work in an environment that has to comply with bank level security.
Thank you!,
David 92595
January 4, 2017 at 1:35 am
It sounds like you want to consume data from an existing web service is that correct? Or are you talking about publishing data natively in SQL server via a web service?
For the later this link will help, but its not somethign I have done outside a test lab and wouldn't really advise doing so either:
http://www.developer.com/net/asp/article.php/3767311/Creating-Native-Web-Services-in-SQL-Server.htm
MCITP SQL 2005, MCSA SQL 2012
January 4, 2017 at 3:01 am
Web services are usually written in C# or similar languages.
The native web services feature mentioned above was deprecated in SQL 2008 R2 and removed entirely in SQL 2012.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
January 4, 2017 at 4:45 am
This really depends on what your trying to do.
I, for example, have to use XML to pass any data to our CRM. Although the CRM does have a SQL database it's only a replication, so changes to the database aren't passed back to the CRM.
To pass the XML, we have to use a Web Service. I therefore create the XML in SQL and store in a table and then use SSIS to loop through any unprocesseed XML. I then have a Package in my SSIS catalog that loops through any unprocessed rows and submits them to the web service. This updates or creates the file in the CRM (which duly creates it in its SQL database).
The web service is on HTTPS, which is something that is secure from a financial perspective (I work in Insurance).
This, however, might be completely irrelevant to you depending on what your goal is. Could you perhaps give us some more information on your requirements. Is the Web service there for receiving data, submitting, both? What do you plan to do with data received, or how will you be generating data you will be submitting?
Give us a basic idea of the flow you want to achieve and we'll be able to give you some much more concise answers 🙂
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
January 6, 2017 at 8:43 am
GilaMonster (1/4/2017)
Web services are usually written in C# or similar languages.The native web services feature mentioned above was deprecated in SQL 2008 R2 and removed entirely in SQL 2012.
Thanks Gail, just shows how long its been since I last looked at that functionality. It never sat well with me publishing data direct from the server as a web service so I'm not really surprised it got deprecated.
MCITP SQL 2005, MCSA SQL 2012
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply