My apologies, I should have been more specific.

The first piece of code runs fine and effectively drops the table.

When the second batch of code is run, that's when...

Thank you, that worked!

Check out this blog, I believe it will give you what you are looking for:

http://cf-bill.blogspot.com/2007/01/select-specific-row-in-sql-server-2005.html

Do not cast the string values in the between clause as datetime. SQL Server already assumes the string is datetime. So when you cast those as datetime, it throws errors.

siweb, try this:

You didn't mention whether or not the values in the between clause are hardcoded, so based on your example I am assuming they are. This works with hard...

Try this:

declare @value varchar(64)

set @value = '2008-08-26 00:00:00'

select @value, CONVERT(datetime, @value)

I created this script a few months ago to show me internal and external fragmentation. The script also shows which options you should run on your indexes, either REBUILD or...

Exactly what I was looking for. Thanks Gary.

1. Make sure your stored procedure is not recompiling every time it is run. (RECOMPILE = ON).

2. Check the index fragmentation using sys.dm_db_index_physical_stats.

3. Check out this post on...

Stored procedures are in my opinion a better choice for security purposes, because they hide the code from the users. So in that respect, implementing a view over a stored...

Instead of dropping the index and rebuilding it, SQL Server 2005 offers a disable option on indexes which is much more efficient.

http://msdn2.microsoft.com/en-us/library/ms177456.aspx

Even though this wouldn't be used for...