I have two databases, one that is being used as forum software for a web application and another in-house application to manage addresses.
I would like to be able to propogate changes from the address application out to the forum application.
On the address application, I put a trigger on insert:
CREATE TRIGGER TACAA_ins
ON dbo.TACAA
FOR INSERT
AS
DECLARE @title varchar(20),
@FName varchar(25),
@LName varchar(25),
@Email varchar(255),
@Passwd varchar(255)
SELECT @title = (SELECT title FROM Inserted)
IF @title = 'Administrator'
use PForums
go
exec Forum.pr_Members_INS_UPD
@Username = @Email,
@Password = @Passwd,
@FirstName = @FName,
@LastName = @LName,
@Email = @Email
But SQL Server says it can't find the PForums.pr_Members_INS_UPD.
Can triggers/stored procedures call one another when they're not in the same database? If not, what would be the better solution?
I would like to be able to propogate changes from the address application out to the forum application.
On the address application, I put a trigger on insert:
CREATE TRIGGER TACAA_ins
ON dbo.TACAA
FOR INSERT
AS
DECLARE @title varchar(20),
@FName varchar(25),
@LName varchar(25),
@Email varchar(255),
@Passwd varchar(255)
SELECT @title = (SELECT title FROM Inserted)
IF @title = 'Administrator'
use PForums
go
exec Forum.pr_Members_INS_UPD
@Username = @Email,
@Password = @Passwd,
@FirstName = @FName,
@LastName = @LName,
@Email = @Email
But SQL Server says it can't find the PForums.pr_Members_INS_UPD.
Can triggers/stored procedures call one another when they're not in the same database? If not, what would be the better solution?