As mentioned already, log backups are critical. I do them every 15-30 minutes on production databases. That helps control the log size, and give you good point-in-time recovery options.

Raghavender (9/7/2010)

---

Perhaps it was initially set as a publisher, and the publication was not completely removed...

There have been several questions asked, that you have not answered, that might provide useful information.

Vivek29 (9/7/2010)

---

Actually its a dev db that needs to be refreshed from prod but space issue is there in dev. I wnat to shrink some other db's datafile in dev...

How much free space is in the database files ?

What command did you run ?

How long did it run ? Did you cancel it ? I had...

SSIS packages in 2005 are more confusing than 2000 DTS packages.

I'm working off memory here, but basically:

With SSIS (not SSMS) You first export the package from "MSDB" to file system...

Unless you have a lot of...

Based on the error message, your database is configured as a publisher for replication. It won't let you truncate the log because replication keeps track of log entries and "knows"...

Is this some kind of homework question ?

Each organization has their own requirements.

Do the SQL error logs give any more detail ?

As I recall, when replicating across domains, I had to create identical accounts on each server with the same password.

Day 1 - Verify that all databases are backed up. If not, back them up.

Don't overwrite...

Matt-1034261 (8/31/2010)

---

So if I had a maintenance plan that backed up the log files every so often, would that maintenance plan also need to do a shrink on the log...

CirquedeSQLeil (8/31/2010)

---

Does defragmenting indexes apply to shrinking log files as well as data files ?