Ai, you are correct. The documentation on the main site was out of date as well as BOL since 64-bit is new. I'll correct that for next time.

I don't think you want to delete and system objects yourself. If they were setup, you want to use EM to remove the subscriptions.

If you really want to, you can...

It needs to be readable by the service account, so if it's on a UNC share, permissions should be granted to the SQL Server service account.

not that big. Done a few million, but that's it.

Steve,

Thanks for that. I'm still tweaking it a little here and there, but Surfinity generously gave us a copy to entice us to use it and I have to say...

The issue has to do with virtual log files. Here's a script that can help

http://www.sqlservercentral.com/scripts/contributions/26.asp

Different questions. a typo in the other one, this one should have been better.

They are similar questions, but different to see if you are reading them or understand the different parts of this. They probably should have been spaced a few more months...

I'm not sure what you mean. Do you mean physical illustrations or txt examples? There are a few articles on the site dealing wiht this.

http://www.sqlservercentral.com/columnists/sjones/intherealworlddisaster.asp

http://www.sqlservercentral.com/columnists/awarren/disasterintherealworld2.asp

http://www.sqlservercentral.com/columnists/bahmed/backupscenariosforsuccessfulsqlserverrestoresandre.asp

insert into TableA

select flag, memberid, ...

from #tmptable

where flag = 'A'

update tableb

set x = y

from #tmptable

where flag = 'C'

etc.

something like this will work if you can determine some "key"

select code, yr, per01

from mytable

where yr = 2003

union

select code, yr, per02

from mytable

where yr = 2003

union

select code,...

Did you either of these?

select count(*) from master.dbo.sysperfinfo

select * from master.dbo.sysperfinfo

Do they both return 0 rows? I'd guess that there is something wrong with the SQL installation in getting counters....

Block them at the router/firewall. If it's a DMZ, you can do that.

Most likely the cookie is on your machine for someone else's login. I'd try logging out and back in again.

Pls don't cross post, we check all the forums. Answered in another thread.

http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=92&messageid=129930