5

I have a table on SQL and when there is an insert to this table I want to print this inserted data.

What I am thinking in:

  1. Create a trigger on that table.
  2. Handle the printing event on c# after the trigger works.

My problem

I don't know what is the name of the feature that makes a c# code fires when a trigger fires.

Can you help me with this issue, please?

Kindle Q
  • 944
  • 2
  • 19
  • 28
RE RE RE RE
  • 209
  • 2
  • 6

1 Answers1

1

There are several ways of solving this problem, and the soluton depends on the system architecture (permissions, accesibility), and the knowledge to implement it.

There are basically this options, which are affected by the pointed out factors:

  • printing directly from the inserting application or notifying from the inserting application: can you change that application? is it possible to comunicate from tha application to the printing application. (It could be implemented, for example, with WCF)
  • sql dependencies (SQL Notification request): the printing application should create and subscribe to a sql dependency: do you have permission to create the dependencies in the server?
  • polling: is the quick & dirty solution: use a "timer" to check if there is new data and print it when available

The last solution is the one that will pose the least problems. It's not "smart" but it's very easy to implement. You can adjust the polling period depending on the expected number of messages and the "real-time" requirements of the pringing application.

JotaBe
  • 38,030
  • 8
  • 98
  • 117
  • I am thinking of the sql dependencies, i have all permissions . my manager sees the last solution is better. i have to choose . what do you think? – RE RE RE RE Sep 01 '14 at 09:57
  • 1
    If you have nothing against the polling solution, implement it, and you'll spare some headeaches. I'd choose that. – JotaBe Sep 01 '14 at 10:46