In case anyone needs a humorous break: http://www.youtube.com/watch?v=KiFKm6l5-vE

Do not ever, ever, ever drop a database without a backup. Even if it's development. Take a backup, store it somewhere, at least for a few months.

Well the Rockies are doing slightly better.

However I'm not. Played a double header yesterday, 1-5, BB. My season is going downhill.

I don't think it's ever mattered, but I second Gail's note. It doesn't matter.

You should enable logging, that will help to determine what is wrong and give more information.

Are you running the job or plan? Do you have a log file setup in the plan?

How are you querying it? Same query? same permissions/user account?

varchar(50) shouldn't be an issue in terms of size/type.

http://msdn.microsoft.com/en-us/library/ms151799.aspx

Shared distributor, recommended this is remote from both servers. I suppose that if I had to put it on a server, I'd put it on the mirror server, not the...

I think I'd use OPENQUERY and send the data range across

select ...

from OPENQUERY( .., 'select dataIneed from other table where date > ' + @begin + ' and date...

I typically do this

BEGIN TRAN

DELETE xxx

if @@Error <> 0

begin

rollback transaction

return 1

end

UPDATE xxx

if @@error <> 0

begin

rollback transaction

return 2

end

commit transaction

I...

I usually set up system database separate from user databases, especially since system databases don't need transaction log backups.

Otherwise, the advice above looks good.

I haven't heard of this. Couple questions:

- Are the drives available in Windows and unavailable in SQL Server or unavailable in both?

- When you remap, what do you run?

I've always had to build a separate table and maintain it. Something like

Period Date

1 1/1/2000

1 ...

Each item in the connection string is a separate entry. You just add the failover partner part.

The Integrated Security clause is an either/or with the uid/pwd section.

Where did you get this link? Or which script should it be?