UDT's are present and supported in SQL server 2005

however defaults and rules are deprecated (they still work, but you can't edit them or create new ones

if it's the connection then that problemw ould apply to all commands issued, not just xp_cmdshell

have you tried a simple xp_cmdshell 'Dir c:\' command to check other xp_cmdshell actions

or try...

agreed

SELECT MediaNewsId, MediaNewsHeadline, MediaNewsReleaseDate, MediaNewsBody

FROM CC_MediaNews

WHERE (PublishOnIntra = 1 OR @READONLY=1) AND StoryStatus = 4 AND MediaNewsReleaseDate <= GetDate() AND Project = @ProjectID

ORDER BY MediaNewsHeadline

i think is what Preethiviraj...

eek - it sounds like you have a few problems !!

A couple of suggestions here

- ensure your database transaction logs are backed up or databases are in simple mode....

can you post examples of a query where this happens?

take the database offline ASAP- take a copy of the files to a new array or remote location and check the disk out

problems with the disk could lead to corruption...

i'd also advise the following changes

if update (Inaktiv)

begin

if (select Inaktiv from inserted)(select Inaktiv from deleted)

begin

INSERT INTO ....

end

end

that way your trigegr doesn't fire when you update a row but set it's...

CREATE PROCEDURE spGetNews

@ProjectID Int,

@ReadOnly bit

AS

set nocount on

if @readonly=1

begin

SELECT MediaNewsId, MediaNewsHeadline, MediaNewsReleaseDate, MediaNewsBody

FROM CC_MediaNews

WHERE StoryStatus = 4 AND MediaNewsReleaseDate <= GetDate() AND Project = @ProjectID

ORDER BY MediaNewsHeadline

end

if @readonly=0

begin

SELECT MediaNewsId, MediaNewsHeadline,...

this sounds a little like the SQL service account may not have the relevant permissions for command executed by xp_cmdshell

although it's just a wild stab in the dark

i'd also suggest the following change

CREATE TRIGGER InsteadUPDATERegistrationTrigger on Registration

INSTEAD OF UPDATE

AS

if update(username)

begin

if (select inserted.username...

jeff,

i'm not sure why you're using triggers for this - can't you just put a unique constraint on the username field?

that would be a lot simpler

my advice from recent experience with asp(.net) is to use Stored procedures to retreive data and update data

your stored procedure to update the tables could easily perform multiple update statments...

is this via enterprise manager, query analyser etc?

if so (and i'm assuming that the server IP address hasn't changed, protocols haven't been disbled and that ther are no problems with...

Thanks for your help on that one -

i had planned to paste these as stored procedures, but for the purposes of development i've used sql until the customer approves...