can you find traces of your missing in action mail in these objects ?

use msdb

go

exec sysmail_help_queue_sp -- @queue_type = 'Mail'

go

select *

-- delete

from sysmail_event_log

order by log_date desc

select *

from sysmail_mailattachments

select...

Just prepare your action a little bit, so you don't end up having a dozen of similar indexes.

No. SA is the sql user which is sysadmin !

It is not the service account!

Do you have your sqlinstance in Mixed authentication mode ?

hmm ... a whole bunch of clustered index scans.

That indicates absence of usable indexes for the predicates you provided.

Even tough stats indicate only 1 row to return, it...

Does your SA password match your domain password policy ?

(maybe even change it temporary during the upgrade only)

Thank you for the feedback.

HTH

2 Tim 3:16 (3/10/2009)

---

even for 64-bit, you still need to "lock pages in memory"

Open the Group Policies Console:

START-RUN , enter - gpedit.msc

Computer Configuration - Windows Settings - Security...

Most of...

thieuquanghuy (3/9/2009)

---

...

Thanks marina.kudryashov, I wonder if Idera is a shareware.

Thanks ALZDBA, this link http://www.sqlservercentral.com/articles/Administration/64974/ is very useful.

and article in http://www.sqlservercentral.com/articles/Security/66151/ is interesting.

I replace FOR LOGIN_EVENT with FOR LOGON, but...

ehm .... tcp/ip enabled for that sql-instance ?

I second RBarryYoung's solution.

That's also how we do it if we want to have our own procedures applicable for 3th party databases.

You could use synonyms in your own db...

/*

http://blogs.solidq.com/EN/rdyess/Lists/Categories/Category.aspx?Name=Memory

I noticed that I could quite a bit of basic memory information from the system

information, so I thought I would show you a very basic query you could use...

To get your inventory of which db-users to synchronize, you can use this script:

You need to run this script in every database of the sql instance !!!

print 'print @@servername...

I forgot to reply on your logon trigger.....

Read my little article regarding exactly that:

http://www.sqlservercentral.com/articles/Administration/64974/

But If you're on sp3 you shouldn't have the problems I encountered.

I also advise to read todays...

you will have to implement it on each and every individual table you want to monitor.

create trALL_yourtable on yourschema.yourtable

for insert, update, delete

as

begin

set nocount on

.....

end

I would advise to log to a...