I don't think we have a big problem here as I don't find a lot of unanswered posts. We used to add a stock answer to a question after 24...

You can build an app for this, but I don't think Reporting Services will work with a table of users.

T-Log backups is a good idea if you are getting lots of new data or changing new rows. If you have lots of changes to existing rows, you could have...

The thing that we've done in the past is schedule a bunch of log backups during the import time. Then make sure that your imports are in smaller batches, not...

It sounds like you have an extremely large db. The diff should be fine, but keep in mind that without more full backups, you are risking data loss if something...

There are some good reporting services articles here on the Site that implement some of the features that you get with Enterprise with Standard. They might help you with the...

Tammy,

We aren't typically annoyed by beginner questions. Even silly ones, but what does get to be "worse" in our minds is the people that don't make an effort. Someone that...

Litespeed and SQL Backup allow you to trade off compression for time/resources as well, with different levels. The native SQL 2008 compression is on/off only.

Here, I'll give you a head start: http://technet.microsoft.com/en-us/library/bb522534.aspx

I don't want high performance children. Heck, I need something to hold over them! They can be high performing adults, when I will need them to take care of me...

In terms of cost, you would have to research your situation. 2008 was the same cost as 2005, but 2008 R2 has a price increase.

Why do you want to upgrade?...

If the issue is finding space, then separate filegroups will definitely help. Just didn't want you to think that you could easily piecemeal restore. You can do some filegroup restores,...

It mentions permissions. Your linked server is working, but perhaps that package/module is not one you have rights to call.

I believe that autogrow does require a lock on the files, but it should be part of SQL Server. I'm not sure what you mean by file in use here...

Lowell is correct. You are converting this to a number in this table, and by convention, numbers do not include leading, or trailing zeros after the decimal.