Steve's got a great answer, but I'd like to throw in my 1cent -- after Steve's reply, that's all mine is worth .

The point...

As long as you have a complete transaction log history, I'm fairly sure this would work.  If you have the possibility of an accidental delete though, that's your real problem. ...

The client tools do require VS 2003, and that the other pieces are setup.  That "cannot find SQL Server" error was very misleading in the beta, and I think it's...

A clustered index would mean that SQL knows exactly what data page to write the record.  It doesn't have to search for room and such. For sequential writing, it can help. ...

Does the proxy account have the proper rights to both the database and the SQL directory?  It will need to be able to run DTSRUN.EXE.

As a TEST only, try setting...

The first thing I would do is throw a clustered index on the table, probably by a primary key if you're simply inserting.  Right now the table is organized as...

This may be your problem.  Check to see if there are more than 8 columns.  Another workaround would be to set them all to text.

Hope this at least gives you...

Hi Larry,

There definitely are oddities with the graphing in Reporting Services.  I *think* it's using the Dundas charting engine (could have sworn I saw a Dundas .dll somewhere, but I...

I ran into this problem once, and it had to do with a language setting in the registry, basically setting it to neutral.  Here's the newsgroup post I found via...

You can always use a SQL Maintenance Plan to manage the log file retention.  I personally avoid maintenance plans whenever possible, but if I do need to use them, this...

I got this message working with Beta 2.  What it came down to is that there was a different prerequisite that hadn't been met.  Make sure that IIS is up...

Wow.  Performance has nothing to do with uniqueness.  If there really is duplicate data, then they have a data quality issue -- performance doesn't play into it at all.  Now...

I actually agree with you Frank

What I think though is in this particular situation it will lead to more arguments and frustration.  Who...

Interesting.  Well, given that the account number is the point of a join, I'd make that the clustered index.  SQL then literally orders the records based on account number.  A...

It's comparing pages -- in the table you have a 1:2 ratio, and the index is a 1:1.  Don't worry about any of this data yet --there aren't enough data...