As...

i suspected what gail said, where you have to use a SELECT * FROM VIEWNAME was the only way to do rowcounts for views.

for tables, you can use the indexes...

I've inherited situations like this as well.

this is common issue when you store datatime in a non-datetime field; sometimes you can hope implicit conversiosn will work, but the format...

i saw that no one name was in two or more of the groups, so i'm assuming they have no relations? is that right? or should they be joined on...

yes exactly...at the data entry level, they would actually type the value in...but the data would be processed by the stored proc, and stored in an encrypted fashion.

here's a really...

wendy the devil is in the details;

we'd proably need to see the actual execution plan of the "new" query hitting those 9 tables to offer concrete advice;

that actual execution...

the name timestamp column is very misleading...it's synonym of ROWVERSION is more descriptive.

change your insert to not include the timestamp column...a new value will be created for you automaticaly, just...

typically i've used a stored procedure to do the whole CRUD operations for tables which contain encrypted values...or at least when the encryption is handled at the SQL server level.

then...

wow that's sounds extra wierd. can you give an example?

if you query these two views, there's no data?

select * from sys.dm_exec_connections

select * from sys.dm_exec_requests

or is it specific views?

pretty wide wave of the hands.. "how to i check my server's health"

You'll probably want to define what you want to check, first, as Jeff said. We can help with...

are you running as sysadmin?

some of those views may be filtered for security reasons to just what YOU've done, unless your a sysadmin.

steveb's right on.

pretty sure your issue is the mails erver doesn't like the way you are connecting.

In order to prevent spam, most mail servers are set up to only allow...

if you are installing anything EXCEPt Express editions, then yes, SSMS is included in the install.

if you grab an EXPRESS edition, you'll want to make sure it's a version "with...

trying ot think outside of the box, i think you could create a job that runs sp_who2 and logs the data to a table...that would have less data, of course,...

for tracking DATABASE access, a logon triggers not really going to help you; I'd really suggest using a DML trace instead.

For that logon trigger,

for example, pick the top...