In this case you are using the identity property incorrectly. Identity is a SQL Server proprietary syntax for generating a new number for each row, guaranteed to be higher than...

I also noticed this a while back and wrote about it in my blog.

Here is a procedure that decrypts objects created with encryption.

Also take a look at the tools page at SQLSecurity.com, especially sql2kpwdtools.zip.

No, there is no such identifier attached with each row. If you could tell a little more about what you are trying to achieve then there is most probably one...

Why can't the rows be stored in the same table? On the contrary, the fact that they have their own numbering systems is good since it lets you have them...

How about using application roles? Create an application role that is a member of db_ddladmin or at least is allowed to alter the table(s) necessary for the indexes. Then have...

Unfortunately I do not think Support wants to have anything to do with Yukon yet. Maybe if you have a very good relationship with them.

You can't. A view is a stored static definition that contains a query to build a resultset, to use like a table.

It's in Books Online

And I pretty nice way as well, I think.

As long as the encryption/decryption works, I see nothing wrong with this.

However, do they actually record the number of times that your resume was found for a specific search, or is it just the number of times it was then actually...

Here is an pseudo-code example of how it can be done:

SELECT searchresults INTO #temptable

INSERT INTO searchstatistics FROM #temptable, with searchinfo

SELECT #temptable as output to client

You don't even need to look at how complex the queries for this table will be. It is absolutely not an acceptable design! There is no PK (RecordID cannot be...

Argh. Just lost a quite long post on this.. What it more or less said was just that I feel that often people tend to write as-simple-as-possible "client-side" data access...