Thanks for the speedy response Jeff,

My apologies for my response being late. Here is some further expounding on my problem...

I have a table that is structured as follows:

Create Table...

Hopefully there are still some people that get updates regarding this thread. I have a follow up question as I recently encountered a similar situation to the original problem....

Not sure how everyone is getting this right. The script fails (as i suspected) in SQL 2005, 2K8 and 2K12. Since the first block is not run due...

The answer really also depends on what version of SQL Server you are using. Some versions do not allow a default value of a declared variable to be set,...

mm,

Yes, it is our standard deployment. Local access is preferred in our case.

The output on the remote machine experiencing the problem is nearly identical to yours (different column names...

FYI

The only reason I recommend to rebuild the database is that each revision and release of SQL Server sometimes uses a revised method of creating physical database objects depending on...

All other client protocols are disabled. The only protocol that is enabled is Shared Memory. This is part of our standard configuration for all deployments.

The most recent errors I have noted have all been:

A connection was successfully established with the server, but then an error occurred during the login process. (provider: Shared Memory Provider,...

Have you re-built your database under the new SQL Server?

This appears to be more of a data entry or application based resolution.

It seems that the easiest approach is to have the user entering dates manually be warned about the...

That's because your DROP statement looks like this:

DROP TABLE [dbo].[' + @temporary + ']

It should look more like the following if you are using the @temporary variable:

...

Thanks for the reply.

I will check to see if the data is in the order of the index.

While I check, would the manner of which the insert is taking place...

It appears you are not using the variable [@temporary] properly in it's different contexts. When you are referencing it inside of a quoted string, it needs to be concatenated....

It seems like things aren't so clear when you are using a SAN and your storage administrator is simply carving LUNs out of a large disk group. Chances are high...

The original script worked for me. I had to, of course, change the size of my database; so I delete a significant amount of history, did a full backup...