Help for Performing Updates Across Multiple Servers

Hi,
We have two DataBases Residing on two different Servers. We would like to
set up real time uodates between these two servers.
We have an Inventory System on server A and a Tracking System on Server B.
Now an Transaction in Server B should Update a Certain Table or Tables on
Server A. and vice versa.
I would like people to help me choose the Best soulution for this to work
successfully.
I was leaning towards Linked Servers anfd The making use of triggers. Is
this a Good Option.
But waht happens if the Trigger Fails how do we get the data Across to the
Servers.
Thanks for your help in advance.
Thanks,
Jothi
Don't fire triggers over a network. The latency added by doing this tends to
make such a solution unworkable. Plus if one of the servers go down the
trigger and sometimes the entire server will hang for up to 20 seconds
before failing.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Jothi" <Jothi@.discussions.microsoft.com> wrote in message
news:7F1F3EA8-2719-4A0B-AC57-1F6AB44183CF@.microsoft.com...
> Hi,
> We have two DataBases Residing on two different Servers. We would like to
> set up real time uodates between these two servers.
> We have an Inventory System on server A and a Tracking System on Server B.
> Now an Transaction in Server B should Update a Certain Table or Tables on
> Server A. and vice versa.
> I would like people to help me choose the Best soulution for this to work
> successfully.
> I was leaning towards Linked Servers anfd The making use of triggers. Is
> this a Good Option.
> But waht happens if the Trigger Fails how do we get the data Across to the
> Servers.
> Thanks for your help in advance.
> Thanks,
> Jothi
>
>
|||BTW - your best bet is using distributed transactions.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Jothi" <Jothi@.discussions.microsoft.com> wrote in message
news:7F1F3EA8-2719-4A0B-AC57-1F6AB44183CF@.microsoft.com...
> Hi,
> We have two DataBases Residing on two different Servers. We would like to
> set up real time uodates between these two servers.
> We have an Inventory System on server A and a Tracking System on Server B.
> Now an Transaction in Server B should Update a Certain Table or Tables on
> Server A. and vice versa.
> I would like people to help me choose the Best soulution for this to work
> successfully.
> I was leaning towards Linked Servers anfd The making use of triggers. Is
> this a Good Option.
> But waht happens if the Trigger Fails how do we get the data Across to the
> Servers.
> Thanks for your help in advance.
> Thanks,
> Jothi
>
>
sql

Help for a real newbie

A problem so simple I'm a little embarrassed to post it... I am setting up a trigger in which I want to, among other things, record the network ID of the user who performs the action that triggers the trigger. I know there is a variable or function out there to pull that information, but I can't find it, and have tried every variation of "login logname usr_id network_id....." I can find.

So first.... could somebody please tell me the variable or function that will return that piece of information. And second, if you also could point me to a good place, either in print or on line, to look up that kind of information, I would be most grateful.

Thanks.

Hello Leslie. The first thing to remember, there is no stupid question (well almost never )

The second thing I will point you to is the Downloadable version of the "BOL" (Books On Line).

It can be found here. http://search.microsoft.com/results.aspx?mkt=en-US&setlang=en-US&q=SQL+BOL If you are using SQL 2005 then it will be the 4th link down. You should also be able to access this by hitting F1 in your Enterprise Manager or inside of SQL Studio. Then switch over to the Index.

Then remmeber that most variables in SQL that are global either scoped to the whole server or the current connection will usually begin with a @.@.. Typing the @.@. in the index will get you in the near vicinity.

I personally found the @.@.PROCID which

Returns the object identifier (ID) of the current Transact-SQL module. A Transact-SQL module can be a stored procedure, user-defined function, or trigger. @.@.PROCID cannot be specified in CLR modules or the in-process data access provider.

and @.@.SPID

Returns the session ID of the current user process.

Try both of those and see if one of those does what you are looking for.

Hope that helps. If you have further questions feel free to ask.

|||

Hi Leslie,

I think you're after the SYSTEM_USER function, which will return the windows login name in the form of ADomain\AUser (if the current user has used a trusted win connection of course).

Cheers,

Rob

HELP With THIS MESSAGE

This is what we are getting on the server but I cannot seem to find anything anywhere and i am not real strong in SQL...I am a server guy that is tasked with finding the issue!

Scott H
Weasel101

Event Type: Error
Event Source: MSSQLServer
Event Category: Server
Event ID: 17052
Date: 3/12/2002
Time: 2:45:06 PM
User: ********** (Changed for privacy...sorry)
Computer: MYCOMPUTER (Changed for privacy...sorry)
Description:
Error: 823, Severity: 24, State: 1
I/O error (bad page ID) detected during read of BUF pointer = 0x1431e6c0, page ptr = 0x498f6000, pageid = (0x1:0x403), dbid = 4, status = 0x801, file = f:\MSSQL7\DATA\msdbdata.mdf.
Data:
0000: 37 03 00 00 18 00 00 00 7......
0008: 08 00 00 00 4e 00 54 00 ...N.T.
0010: 30 00 30 00 33 00 32 00 0.0.3.2.
0018: 4b 00 00 00 05 00 00 00 K......
0020: 6d 00 73 00 64 00 62 00 m.s.d.b.
0028: 00 00 ..Do you know if this happened during a restore ?|||There looks to be a Technet article on this problem:

BUG: Error Message 823 or Retail Assert Encountered During Restore of SQL Server Log Backup (Q281809) (http://support.microsoft.com/default.aspx?scid=kb;EN-US;q281809)|||CAUSE
SQL Server may allow the log to be backed up when non-logged operations have taken place.

WORKAROUND
To workaround this problem either:

Avoid the use of non-logged operations.

-or-

Ensure that any process performing non-logged operations complete and secure a complete database backup