Take the 2-minute tour ×
Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. It's 100% free, no registration required.

This question is an exact duplicate of:

I know basic only concepts (DDL,DML queries) of the SQL Server 2012. I explain the workflows of both my application and the database below.

Workflow of the application:

I build web application in Java. Whenever it receives an HTTP request, it fetches data from the database, does some computations on the data and the computed data will be stored in another database.

Before explaining the database workflow, I will explain what a database modification is from my point of view: If any operation happens like creating new tables, data modification, data deletion in tables, etc. indirectly all these are effects on the database.

Workflow of the database:

I have SQL Server 2012. Whenever the database is modified, it will send an HTTP request to the application. The Application runs on an Apache Tomcat server. Once the application receives the HTTP request, it continues that individual workflow.

If you understand my question, we are not sending HTTP requests from a browser (i.e. end-users can't access this application), we are sending HTTP request from SQL Server.

I hope you understand what my question is.

I read some tutorials for this, but I didn't get anything.

Can anyone suggest the correct way of doing this?

share|improve this question

marked as duplicate by dezso, Max Vernon, RolandoMySQLDBA, Paul White, Mark Storey-Smith Jun 24 '13 at 17:31

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

2  
I'm sorry but what is your question? You've explained a complicated setup, but not what part of that you've implemented already and what's missing. What exactly are you looking for help with? –  Mat Jun 24 '13 at 13:32
    
The question is in the title. Really, though, the answer is: don't. You need to refactor/rethink the application architecture. –  Jon Seigel Jun 24 '13 at 14:15

1 Answer 1

You send a request, when you need something back. If you want to let someone to know something, but do not need anything back you notify with a notification.

There is such a feature called SQL Server Service Broker. It allows communitaion over boundaries of different systems and guarantees consistency and timing of the messages.

Further reading: - SQL Server Service Broker on MSDN - SQL Server Service Broker Explained

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.