This statement simply encrypts EXISTING SSNs:

OPEN SYMMETRIC KEY Key_01

DECRYPTION BY CERTIFICATE DatabaseA01

UPDATE dbo.TableA

SET SSN = ENCRYPTBYKEY(KEY_GUID('Key_01'), SSN)

CLOSE SYMMETRIC KEY Key_01

If new records are being encrypted as they are added, you...

Encryption on a column can't be 'turned off.' It's the values in the field that are encrypted, not the column itself. You are probably storing the encrypted SSNs...

Here's an example without a TRY...CATCH block:

IF 1=1

BEGIN

;THROW 51000, 'The record does not exist.', 1;

END

"The statement before the THROW statement must be followed by the semicolon (;) statement terminator."

Try putting a semicolon right before the THROW statement, like:

BEGIN CATCH

;THROW

END CATCH

Yes. You can also do it inline like this:

SELECT

xml_column.query('declare namespace ns="http://webservice.nada.com/"; data(//VehicleValue_Struc/ns:VehicleYear)[1]') AS vehicle_year

FROM

vehicles

WHERE

id = 10

And you are welcome

;WITH xmlnamespaces (N'http://webservice.nada.com/' as ns)

SELECT

xml_column.value(N'(//VehicleValue_Struc/ns:VehicleYear)[1]',N'nvarchar(100)') AS vehicle_year

FROM

vehicles

WHERE

id = 10

OR:

;WITH xmlnamespaces (N'http://webservice.nada.com/' as ns)

SELECT

xml_column.query(N'data(//VehicleValue_Struc/ns:VehicleYear)[1]') AS vehicle_year

FROM

vehicles

WHERE

id = 10

You could set up a login trigger to fire a proc on login that contained appropriate logic. However, any other procs that were executed by a login may have...

I think this might give you some...

I would expect a single transaction log backup when using APPEND, and I'd expect the transaction log backup to grow each hour, until it was replaced by a new backup...

SELECT datediff(mm, dateadd(mm, 48, ADOPTION), getdate()) AS MonthsPastDue

FROM EOP

Do you have a backup? Have you tried the REPIAR_ALLOW_DATA_LOSS option with DBCC CHECKTABLE? If you have a current backup, I would restore the database to a NEW...

bpowers (5/15/2012)

---

The problem I am trying to code out, is that the length of the string will grow over time. However, as it grows I want strip off the first...

Yes - when you use the 'WHEN NOT MATCHED BY' clause, you have to use the keywords 'SOURCE' or 'TARGET'. However, it's ok to alias your actual table names...

Why do you have to use a...

What have you tried so far?