All the good advices. Just to add my 2c, I would prefer to have the auto growth only catering for emergency growths for most of my databases. We plan, or...

Though the question is pretty old, but to help someone in this situation, check if the SQL Server Browser service is running on the subscriber. If not then start the...

For those who want to run this script in SQL Server 2000, here is a slightly modified version that doesn't use msdb.dbo.sysschedules. All the scheduling columns were present in...

I agree with all those who got it wrong by saying "None of the above" as the question was not clear about disk IO.

But I got this one right only...

Is your distributor also on SQL 2012 ?

See if the solution discussed in following link any helpful.

http://social.msdn.microsoft.com/Forums/en-US/sqlreplication/thread/ff2565fb-3f77-427d-bd38-522988baa9e0/

Yes, that's correct.

And if you want to keep the data in default varbinary format and display it in character when selecting then last statement can be changed to display...

This might answer your question

or this one

http://www.sqlservercentral.com/Forums/Topic1085386-391-1.aspx#bm1085485

Almost all database monitoring tools provide interface for Job monitor.

Collation change can become very messy, especially when you're upgrading at the same time. I'm sure you'll be trying out this method before doing it in production system.

Anyhow, I can...

Hi Wayne,

If you're looking at the first column of your resultset (i.e. referencing_minor_id) then that should always be 0 unless your object in the query is of type COLUMN.

In...

Looks like the "monthly" data load is a time consuming SP and running over the default "remote query timeout" period which is 10 minutes (600 seconds).

Try setting this value...

sknox (7/19/2012)

---

bitbucket-25253 (7/19/2012)

---

Stewart "Arturius" Campbell (7/19/2012)

---

anthony.green (7/19/2012)

---

I also read it as being Yes as the question didnt specify needing to delete or not delete the other snapshots, so in theory...

Good that you got your data back.

Another way to avoid such accidental updates is to set "implicit transaction" ON in a session or globally in SSMS.

To enable implicit transactions...

This normally happens when SQL instance is restarted and SQL Server tries to recover the database.

Like other members, I would also recommend checking the server logs to find out...

Thanks Rudy for sharing this wonderful article.

Like other members, I never thought about using single-user mode in this way. I hope I'll never have to use this .

Cheers,

Fahim