ramana3327 (4/15/2014)

---

Hi,

Correct me if I am wrong. I think covering Index is nothing but adding columns that are participating in the where clause right? What about the include columns. What...

Do you have the resource governor running on this...

You database has the space that you've either "given" it or is based upon your auto-growth settings. If you ran out of space I would guess that you have...

?

It's just the output of reads...in a more readable format, there's no actual "data"...

Hardly something to be worried about.

In my experience, this isn't actually an error. It's more of a "Hey! I'm usually pretty busy, but I've got nothing to do right now...you should take a look!"...

What exactly are you trying to find out? The error is pretty specific: the authentication process is timing out.

Try increasing the connection timeout property on the actual linked server...

If you can, please post the exact query, as well as the index definitions.

Most importantly, please attached the execution plan...

To start, add a non clustered index on the filtered column...

smtzac (4/11/2014)

---

one thing, when I ran your 1st script about backup history and I filtered by database_name, I am getting two same backup dates, although I have a backup...

use [PublishedDB]

GO

EXEC sp_dropsubscription @publication= N'PublicationName', @article =N'Table1', @subscriber=N'all'

EXEC sp_droparticle @publication = N'PublicationName', @article = N'Table1', @force_invalidate_snapshot = 1

use [PublishedDB]

GO

EXEC sp_dropsubscription @publication= N'PublicationName', @article =N'Table2', @subscriber=N'all'

EXEC sp_droparticle @publication = N'PublicationName', @article...

I don't believe this is possible other than watching the snapshot run via the GUI, you can however determine the total size of the snapshot. Then, based on your...

I believe you just need to Wrap your @sql in brackets:Execute (@sql); Otherwise, it thinks you are execution a stored-procedure

On the publisher, you can run:use [PublishedDB]

GO

EXEC sp_dropsubscription @publication= N'PublicationName', @article =N'TableName', @subscriber=N'all'

EXEC sp_droparticle @publication = N'PublicationName', @article = N'TableName', @force_invalidate_snapshot = 1

This operation is single threaded in sql 2008 and earlier and can only take advantage of 1 CPU (this is why it takes so long) I believe it is multi-threaded...

Tables, views, procedures, and functions are stored in the DistributionDB.dbo.MSarticles table:SELECT * FROM distribution.dbo.MSarticles WHERE publisher_db = [YourDB]

Hope this helps!

Also, on the publisher you can run the query below to...

Okay...

To collect database growth over time, you could use something like this: SELECT database_name ,

BackupDate = CONVERT(VARCHAR(10), backup_start_date, 111) ,

SizeInGigs =...