Or, have an NMR Number, plus an Identity column.

From moving over to the new system, NMR = the Identity column for all new values with the Identity column providing the...

Hey - what's cryptic about ttdsls045400? 😛

If you're going to build it - then you can simply make an addition to your CRUD procs to insert into an audit table;

spTableInsert ( ... params)

INSERT table fields ......

Is this a third party app, an in house app using sp's for updates inserts and deletes or a scary inhouse app using all kinds of passthrough and general nastyness?

What exactly is it you're being asked to monitor?

Build the DOS copy command string and assign it to a variable such as @Cmd, then use xp_cmdshell

eg

DECLARE @Cmd VARCHAR(4000)

... build DOS command and assign to @Cmd

EXEC master..xp_cmdshell @Cmd

Glad to have been of assistance

SUBSTRING(RTRIM(WhateverColumn), 1, LEN(RTRIM(WhateverColumn)) -1)

AND

WHERE

RIGHT(RTRIM(WhateverColumn), 1) = 'L'

should get you sorted Matt

Aye - just bung in an RTRIM()

Or better, come to think of it ....

UPDATE tblWhatever

SET whateverColumn =

CASE Surname

WHEN 'Gothard' THEN

CAST(

600 +

CAST

(

SUBSTRING(WhateverColumn, 1, LEN(WhateverColumn) -1) As INT

)

As VARCHAR(10)

)

+ 'L'

ELSE

CAST(

60 +

CAST

(

SUBSTRING(WhateverColumn, 1, LEN(WhateverColumn) -1)...

Well - roughly, something like this would do it;

UPDATE tblWhatever

SET whateverColumn =

CAST(

60 +

CAST

(

SUBSTRING(WhateverColumn, 1, LEN(WhateverColumn) -1) As INT

)

As VARCHAR(10)

)

+ 'L'

WHERE

RIGHT(WhateverColumn, 1) = 'L'

BUT - if you were...

CREATE FUNCTION [dbo].[TRUNC]

(

@datInDATETIME

)

RETURNS DATETIME

AS

BEGIN

RETURN CAST(FLOOR(CAST( @datIn AS float))AS datetime)

END

CREATE PROCEDURE spMyProc

(

@datStartDATETIME= NULL

)

AS

DECLARE @datEndDATETIME

SELECT @datStart = COALESCE(@datStart, dbo.TRUNC(GETDATE()))

SELECT @datEnd = DATEADD(Day, -7, @datStart)

etc...

Also some decent stuff on http://www.sqlis.com/

Ross McMicken (9/17/2008)

---

I have to wonder why anyone would ever consider keeping unrelated data in the same database. Separate databases provide the security and segregation that good internal controls require....

Have you set up the Oracle drivers, TNSNAMES and SQL.ORA files on the report server?