How big are your .mdf and .ldf files? Is the database in full recovery mode? If so, are you performing transaction log backups with some regularity to keep the log...

I wnet back and forth on /3GB and AWe for a while. Here's a link that should help. May not tell you EXACTLY what you're asking but it should help...

I used SQLSafe and Lightspeed. Comparable in functionality, both very good products. It came down to purchase price and maintenance costs.

If the databases are small and not of particular criticality ("Again, these are light database with few usage and little importance so to say."), one server should be fine. The...

Can you backup locally via SQL and then move the backup files to a network share for longer term storage? Leave one day on local disk and maybe a week...

Arthur.Lorenzini (8/27/2008)

---

What would be the best approach to restoring the production database to our development server? The production data file is 568GB in use and allocated to 59GB and the...

KDASQL (8/29/2008)

---

Have the maintenance plan delete any files older then 24 hours - this way any time you do a backup you will automatically delete the last backup since you...

Granted, initially only one...

Use \\computername\sharename in your backup file location. If you don't know the serve or share name, you're basically out of luck. You cannot map a remote drive as SQL will...

Several different ways to the same result.....

I do full backups on Sunday. I do logs during the weekdays, every hour. On weekday evening, I do differential backups. The logs will...

While it's not recommended, you can backup to a UNC path. Be sure the account running the SQL Agent has rights to the share. GSquared's approach is the preferred method...

As it should be. Not a part of "best practices" as most of us are aware. It should only be used in rare circumstances, if at all. Size your log...

Jeffrey Irish (8/29/2008)

---

No need to set auto-shrink. As Ray Mond says, it can cause more harm than good.

If you backup your Transaction Logs frequently enough that is typically adequate to...

I haven't used this much - yet. A colleague of mine at a previous job liked it well enough.

http://www.dotnetjunkies.com/

It appears that it could be a SQL bug (refer to link below) but you haven't really provided much information to go on. What version of SQL are you running...