usually you see this message when you have autogrow enabled, but when a transaction needs more space than the autogrow will allow, or you have autogrow turned off for that...

This has already been asked and answered here... http://www.sqlservercentral.com/Forums/Topic575393-65-1.aspx.

Please don't multi post.

-Luke.

Unfortunately when you are connecting access to SQL server via Linked tables, every time you query a table with a join access will pull the entire thing down to the...

Since you're interested in both data and structure, why don't you just restore the previous night's backup from the production server to test and dev?

Alternatively you could check...

It's all about the rounding during the conversion from your character string to a datetime. As you noted SQL server is only acurrate to 1/300th of a second.

.999...

Instead of Using Select Into Use Insert Into.

Select Into create a table, while insert into inserts data into an existing table. BOL has a good reference describing the differences.

I'm pretty sure that given this requirement I would protest as loudly as possible, and even get it in writing that you disagreed with this requirement and you have explained...

did you install any of the Service Packs as you hadn't yesterday. Is the server set to automatic updates and it perhaps installed them and rebooted over night?

Are you...

Your performance killer is here...

79% - Table Scan on REVENUE_FACT

It's not using indexes that are appropriate and is instead using a table scan. What indexes are defined for that...

you are grouping by one less column in your query, that could be the difference. Try pulling some of your join predicates back out into the where statement and...

I'm not an expert on looking at statistics and being able to tell you what they mean...

I do better with execution plans, so I'll just drop back and punt on...

At this point the only way to do that, unless you are using partitioning, would be to do take a backup of your database (db1) and restore it to a...

If you don't use an ELSE in your CASE statement, whenever the expression returns false you get a NULL.

Also think about the order in which the rows might have been...

All that would do would perhaps provide a bit better readability for you.

If however some of the join conditions were added to the inner join specification you may see some...

What about like this? The N prior to the value forces it's use as a Nvarchar string.

SELECT EventNumber, ViolationNumber

FROM ...