That's a good strategy. Let me ask, why not ship the logs to 2012 directly?

Also, remember that upgrading an instance is much more than just upgrading the databases: you will...

As others have pointed out, changing the collation for a database is not simple.

However, if you need to change it it's probably because some comparisons between columns in your database...

Assigning a default schema to a group is not possible in SQL Server until 2012. All previous versions (including 2008 R2) do not allow this.

Granting permissions is a whole different...

From BOL:

In other words, no. Not directly at least.

You can always wrap...

Not that I'm aware of.

Some way you have to download the file to the filesystem, using BCP, a custom application or a CLR procedure.

However, DBMail doesn't look to me like...

yuvipoy (4/25/2014)

---

Is it a good practise to have my tables in different files.

Say i am having 10 master tables.

Can i create tables each one on 10 secondary files(.ndf) in a...

You just need to drop the publications then.

You can do it manually in SSMS by clicking the publication and hitting DEL.

You can also do it in T-SQL.

See if this helps:...

Alexandre Araujo (4/24/2014)

---

My question is why a start service like agent is logged and a...

"Enterprise manager"... are you sure it's a SQL Server 2008?

Anyway...T-SQL job steps run under the job owner security context.

However, if the job owner is a sysadmin, the step will...

sp_msForEachDB would do.

You could also check out my humble replacement[/url]

Not everything gets logged to ERRORLOG.

Something gets logged to the default trace, something gets logged to the system health session, something is not logged at all unless captured by audits...

Log to where? SQL Server Log (ERRORLOG)?

Remember that you also have the default trace. Something (including create/drop database) gets logged there.

BTW, writing all caps in forums is perceived as shouting and it is considered bad and unpolite.

I suspect you have no publishing/distribution to disable.

Run this:

SELECT name, is_published, is_merge_published

FROM sys.databases

If any of your databases is published, you should see "1" in the "is_published" or "is_merge_published" columns.

If your...

I think it's the procedure call that generates the error, not the procedure per se, unless you have dynamic code in your procedure.