| Groups | Blog | Home |
sql server new users : Need to interface MS SQL in C++...
We need to find if MS SQL has an API for connecting C++ components to it. We don't know if "extended stored procedure (xp)" is the way to go. Why do we need that ? We must implement a synchronization software layer to make sure an ODBMS has the same values as those contained in an MS SQL RDBMS. Our client applications must use the data in such a way that doesn't fit with the relational paradigm... But the data must be stored in relational fashion for it needs to be easily extracted or used by our customers. We would like something that follows the "Observer Pattern" to notify an ODBMS that a table was modified through the standard "Create", "Update" or "Delete" events. In fact, it would do more than just notifying. It would actually push the modified values to the ODBMS space to update it. It would also need to do the opposite. (i.e. Push modified values from the ODBMS domain to the RDBMS one.) Thanks for any help ! _________________________ Acoquinar
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1 Before worrying about C++ routines I'd use the SQL Server's Linked Server ability; then apply triggers to the SQL'r tables you want in "Observer Pattern" that will "push" the data on the ODBMS db. Conversely, if the ODBMS db has triggers, create them on the tables that you want to "push" data into the SQL Server db. See any db design book for more info on Triggers; or, look in SQL Server's Books on Line (BOL) for info on triggers and Linked Servers. -- MGFoster:::mgf00 <at> earthlink <decimal-point> net Oakland, CA (USA) -----BEGIN PGP SIGNATURE----- Version: PGP for Personal Privacy 5.0 Charset: noconv iQA/AwUBQbYuFIechKqOuFEgEQK9UACfVEtTsRQuy1fNdoBOnXVR85Z2Kw4AoN8j s2fiH6EHoE1LqVGrbZZh55lp =WLkd -----END PGP SIGNATURE----- [quoted text, click to view] acoquinar wrote:
> Greetings ! > > > > We need to find if MS SQL has an API for connecting C++ components to it. > > We don't know if "extended stored procedure (xp)" is the way to go. > > > > Why do we need that ? > > > > We must implement a synchronization software layer to make sure an ODBMS has > the same values as those contained in an MS SQL RDBMS. Our client > applications must use the data in such a way that doesn't fit with the > relational paradigm... But the data must be stored in relational fashion for > it needs to be easily extracted or used by our customers. > > > > We would like something that follows the "Observer Pattern" to notify an > ODBMS that a table was modified through the standard "Create", "Update" or > "Delete" events. In fact, it would do more than just notifying. It would > actually push the modified values to the ODBMS space to update it. > > > > It would also need to do the opposite. (i.e. Push modified values from the
[quoted text, click to view]
"acoquinar" <acoquinar@hotmail.com> wrote in message news:#IwoAJJ3EHA.1192@tk2msftngp13.phx.gbl... > Greetings ! > > > > We need to find if MS SQL has an API for connecting C++ components to it. You mean develop your own components for SQL Server? [quoted text, click to view] > We don't know if "extended stored procedure (xp)" is the way to go. -snip- > Why do we need that ? -snip- > We must implement a synchronization software layer to make sure an ODBMS has > the same values as those contained in an MS SQL RDBMS. Our client > applications must use the data in such a way that doesn't fit with the > relational paradigm... But the data must be stored in relational fashion for > it needs to be easily extracted or used by our customers. > We would like something that follows the "Observer Pattern" to notify an > ODBMS that a table was modified through the standard "Create", "Update" or > "Delete" events. In fact, it would do more than just notifying. It would > actually push the modified values to the ODBMS space to update it. Surprising the technology you want is called Notification Services http://msdn.microsoft.com/library/default.asp?url=/library/en-us/sqlntsv/htm /nsp_programmingguide_8neb.asp
Our goal is really just to create a "Replication" mechanism like the one
associated with SQL Server. The difference is that we don't wish to syncronize between more than one SQL Server instances...We wish to synchronize between a central MS SQL Server and remove ODBMS servers. It implies a intence synchronization for any DML operations (i.e. "Insert", "Delete" or "Update") that would occur on the SQL Server instance. Which entry point or API could we use to do that ? P.S. "Notification Service" doesn't seam to be an API for sending notifications based of events that occur in the tables. (Correct me if i am wrong here !) Thanks ! [quoted text, click to view] "CJ Llewellyn" <invalid@example.con> wrote in message news:%23%23059UL3EHA.2540@TK2MSFTNGP09.phx.gbl... > "acoquinar" <acoquinar@hotmail.com> wrote in message > news:#IwoAJJ3EHA.1192@tk2msftngp13.phx.gbl... > > Greetings ! > > > > > > > > We need to find if MS SQL has an API for connecting C++ components to it. > > You mean develop your own components for SQL Server? > > > We don't know if "extended stored procedure (xp)" is the way to go. > -snip- > > Why do we need that ? > -snip- > > We must implement a synchronization software layer to make sure an ODBMS > has > > the same values as those contained in an MS SQL RDBMS. Our client > > applications must use the data in such a way that doesn't fit with the > > relational paradigm... But the data must be stored in relational fashion > for > > it needs to be easily extracted or used by our customers. > > > We would like something that follows the "Observer Pattern" to notify an > > ODBMS that a table was modified through the standard "Create", "Update" or > > "Delete" events. In fact, it would do more than just notifying. It would > > actually push the modified values to the ODBMS space to update it. > > Surprising the technology you want is called Notification Services > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/sqlntsv/htm > /nsp_programmingguide_8neb.asp > > >
Our goal is really just to create a "Replication" mechanism like the one
associated with SQL Server. The difference is that we don't wish to syncronize between more than one SQL Server instances...We wish to synchronize between a central MS SQL Server and remove ODBMS servers. It implies a intence synchronization for any DML operations (i.e. "Insert", "Delete" or "Update") that would occur on the SQL Server instance. Which entry point or API could we use to do that ? P.S. "Notification Service" doesn't seam to be an API for sending notifications based of events that occur in the tables. (Correct me if i am wrong here !) Thanks ! [quoted text, click to view] "CJ Llewellyn" <invalid@example.con> wrote in message news:%23%23059UL3EHA.2540@TK2MSFTNGP09.phx.gbl... > "acoquinar" <acoquinar@hotmail.com> wrote in message > news:#IwoAJJ3EHA.1192@tk2msftngp13.phx.gbl... > > Greetings ! > > > > > > > > We need to find if MS SQL has an API for connecting C++ components to it. > > You mean develop your own components for SQL Server? > > > We don't know if "extended stored procedure (xp)" is the way to go. > -snip- > > Why do we need that ? > -snip- > > We must implement a synchronization software layer to make sure an ODBMS > has > > the same values as those contained in an MS SQL RDBMS. Our client > > applications must use the data in such a way that doesn't fit with the > > relational paradigm... But the data must be stored in relational fashion > for > > it needs to be easily extracted or used by our customers. > > > We would like something that follows the "Observer Pattern" to notify an > > ODBMS that a table was modified through the standard "Create", "Update" or > > "Delete" events. In fact, it would do more than just notifying. It would > > actually push the modified values to the ODBMS space to update it. > > Surprising the technology you want is called Notification Services > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/sqlntsv/htm > /nsp_programmingguide_8neb.asp > > >
Correction,... (REMOTE instead of remove)
The difference is that we don't wish to syncronize between more than one SQL Server instances...We wish to synchronize between a central MS SQL Server and A REMOTE ODBMS servers. [quoted text, click to view] "acoquinar" <acoquinar@hotmail.com> wrote in message news:OLRDFkV3EHA.3716@TK2MSFTNGP10.phx.gbl... > Our goal is really just to create a "Replication" mechanism like the one > associated with SQL Server. > > The difference is that we don't wish to syncronize between more than one SQL > Server instances...We wish to synchronize between a central MS SQL Server > and remove ODBMS servers. > > It implies a intence synchronization for any DML operations (i.e. "Insert", > "Delete" or "Update") that would occur on the SQL Server instance. > > Which entry point or API could we use to do that ? > > P.S. "Notification Service" doesn't seam to be an API for sending > notifications based of events that occur in the tables. (Correct me if i am > wrong here !) > > Thanks ! > "CJ Llewellyn" <invalid@example.con> wrote in message > news:%23%23059UL3EHA.2540@TK2MSFTNGP09.phx.gbl... > > "acoquinar" <acoquinar@hotmail.com> wrote in message > > news:#IwoAJJ3EHA.1192@tk2msftngp13.phx.gbl... > > > Greetings ! > > > > > > > > > > > > We need to find if MS SQL has an API for connecting C++ components to > it. > > > > You mean develop your own components for SQL Server? > > > > > We don't know if "extended stored procedure (xp)" is the way to go. > > -snip- > > > Why do we need that ? > > -snip- > > > We must implement a synchronization software layer to make sure an ODBMS > > has > > > the same values as those contained in an MS SQL RDBMS. Our client > > > applications must use the data in such a way that doesn't fit with the > > > relational paradigm... But the data must be stored in relational fashion > > for > > > it needs to be easily extracted or used by our customers. > > > > > We would like something that follows the "Observer Pattern" to notify an > > > ODBMS that a table was modified through the standard "Create", "Update" > or > > > "Delete" events. In fact, it would do more than just notifying. It would > > > actually push the modified values to the ODBMS space to update it. > > > > Surprising the technology you want is called Notification Services > > > > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/sqlntsv/htm > > /nsp_programmingguide_8neb.asp > > > > > > > >
[quoted text, click to view]
"acoquinar" <acoquinar@hotmail.com> wrote in message news:uTFzhmV3EHA.2316@TK2MSFTNGP15.phx.gbl... > Correction,... (REMOTE instead of remove) > > The difference is that we don't wish to syncronize between more than one SQL > Server instances...We wish to synchronize between a central MS SQL Server > and A REMOTE ODBMS servers. <quote copyright="Microsoft"> A notification can be generated and sent to the user as soon as a triggering event occurs. Or, a notification can be generated and sent on a predetermined schedule specified by the user. The user's subscription specifies when the notification should be generated and sent to the user. Notifications can be sent to a wide variety of devices. For example, a notification can be sent to a user's cellular phone, personal digital assistant (PDA), Microsoft Windows Messenger, or e-mail account. Because these devices often accompany the user, notifications are ideal for sending high-priority information. </quote>
That is why we say that it's probably not what we're looking for.
We're not looking for a User Oriented feature but an API that allows us to trigger synchronization routines based on any transactions made in a DB. We probably something more low-level no ? [quoted text, click to view] "CJ Llewellyn" <invalid@example.con> wrote in message news:uOo2keX3EHA.3336@TK2MSFTNGP11.phx.gbl... > "acoquinar" <acoquinar@hotmail.com> wrote in message > news:uTFzhmV3EHA.2316@TK2MSFTNGP15.phx.gbl... > > Correction,... (REMOTE instead of remove) > > > > The difference is that we don't wish to syncronize between more than one > SQL > > Server instances...We wish to synchronize between a central MS SQL Server > > and A REMOTE ODBMS servers. > > <quote copyright="Microsoft"> > A notification can be generated and sent to the user as soon as a triggering > event occurs. Or, a notification can be generated and sent on a > predetermined schedule specified by the user. The user's subscription > specifies when the notification should be generated and sent to the user. > Notifications can be sent to a wide variety of devices. For example, a > notification can be sent to a user's cellular phone, personal digital > assistant (PDA), Microsoft Windows Messenger, or e-mail account. Because > these devices often accompany the user, notifications are ideal for sending > high-priority information. > > </quote> > >
[quoted text, click to view]
"acoquinar" <acoquinar@hotmail.com> wrote in message news:uhByraf3EHA.2608@TK2MSFTNGP10.phx.gbl... > That is why we say that it's probably not what we're looking for. > > We're not looking for a User Oriented feature but an API that allows us to > trigger synchronization routines based on any transactions made in a DB. > > We probably something more low-level no ? No, the notification server is designed to allow messages to be dispatched to different subscribers in different formats over a wide variety of protocols. The main examples given in the book are to human receipients, however the technology works just as effeciently and effectively for other applications and systems. You'll see that the API has support for both subscribing to notifications as well as being able to send and receive notifications.
Don't see what you're looking for? Try a search.
|
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |