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

You can give create permission, but drop goes to teh table owner. I'd give them create under their user name, so they'd create tables as

bill.mytable

You can use sp_changeobject_owner to move...

Not that I know of. Lumigent's Log Explorer, Log PI, Apex SQL, all have tools to read the log. I built one awhile ago, but it had flaws.

Big hammer held...

It should be related to backup and recovery. Lost tape, backup failed, not checked, restore didn't work becaues of paths, server blew up, had to cobble one from desktops, ...

temporary tables, assuming this isn't a ##mytable and it a #mytable, are unique to each person. Even if you create the same name, SQL server will change the name internally...

I agree that text would be better. If you want to try and save space, you could set the text_in_row for this table to 1000 or 1500 and get all...