I don't think so. I tried it with no success.

Cheers,

- Mark

Restore a backup of the backup server's original master.

If you didn't realy want to clone the server, then a restore of master is not for you. You'll need to...

Sounds interesting. I'm always keen to learn something new. Can you post an example?

Cheers,

- Mark

Refer to QOD Aug 4 2003... TABLE variables cannot be passed to SPs (either as input, or output).

Looks like you've come across the other limitations of TABLE variables too. ...

Apparently EM only supports pasting of up to 1024 chars.

This limitation is seriously under-documented.

There's no workaround that I know of.

Cheers,

- Mark

Now that Chris has mentioned it, I do recall having seen situations where people have coded "bypass" facilities into triggers. In a case I recall, the session's CONTEXT_INFO was...

...and, just to confuse the us, the CURRENT_TIMESTAMP system function DOES return the current date/time as a datetime datatype.

TIMESTAMP is a valid date/time datatype in DB2, so don't get it...

Here's a possibility...

 

select * from EMPMASTER  (xlock,rowlock,readpast) where EMPLOYEECODE = '100'

IF @@ROWCOUNT = 0 AND EXISTS (select * from EMPMASTER (nolock) where EMPLOYEECODE...

A couple of things that come to mind:

1) for the redundant databases (data derived from operational systems) you might want to consider placing them on a simple RAID-0 set. This...

quote:

---

What is possible to encrypt in SQL server

triggers ?

SP's ?

Views ?

---

yes,yes,yes.

Also, functions.

Note that the...

Look on the bright side....

1) you're at a company that's actually spending money

2) if anything gets queried in the future, you and the boss can blame the consultant (sort of...

From master database in QA, you should be able to do something along the lines of:

 

restore database [MyDB] from disk = 'TheFullBackup.bak' with norecovery

restore database...

I rarely use EM to restore master. That's not to say it can't be done, but the command prompt process I follow is along the lines of:

Good to see.

An observation though... you're using a separate table for the "next customer id". This has the potential to get out of sync or to cause locking/blocking problems,...

Can you re-post the current code?

Cheers,

- Mark