I think this might be what you are looking for:

http://www.red-gate.com/products/sql-development/sql-dependency-tracker/[/url]

Also add onto that, if you want to use, or are using alerts you need agent running.

I agree with G, too... if you're running any agent jobs, you need...

SQL Server and SSRS won't track that in the database at all.

I see...

The error means that you restored one of your filegroups farther forward in time than you did the other.

You'll have to restore them to the same point in time then...

I should have also said, you may need to synch the login sids and add logins on the new server to allow access.

after you add logins, use the database and...

you forgot one last step

RESTORE database UMyDB with recovery;

This information is stored in the system views.

select * from sys.service_queues

here's a link to the famous poster:

http://www.microsoft.com/download/en/details.aspx?id=9301

Yes, but that is the claim of the first poster's quote... that it is not a windows clustering problem but a problem in SQL Server.

from here: http://msdn.microsoft.com/en-us/library/ms189910.aspx

"

SQL Server...

The correct answer is that it listens on all IP addresses on UDP 1434.

IP_ANY refers only listening on any IP address that is bound to the host including all cluster...

We were recently told by MS that for Windows 2008 R2 clustering that the drive letter is required for SQL Server.

In SQL 2005 we used Veritas clustering which...

Take a log backup, then do the shrinkfile.

Use the truncateonly option in shrinkfile to release all the space after the log truncation point.

seth delconte (7/13/2011)

---

SQLBOT (7/13/2011)

---

Pretty sure you need to stick with full recovery for mirroring, Seth.

You also don't need to set the recovery model to simple for using dbcc shrinkfile.

In your...

not quite sure what you're getting at, but here's my attempt.

create role role1 authorization dbo

create role role2 authorization dbo

exec sp_addrolemember 'db_datareader','role1';

exec sp_addrolemember 'db_datareader', 'role2';

exec sp_addrolemember 'db_datawriter','role2';

now you just need to...

If you can insert records in the order of the clustered index, you won't have as much fragmentation because the inserts are appended onto the end of the index instead...