If you check sysindexes in both DBs, you will see that they are not in fact the same -- the DB with no data will have fewer rows in sysindexes,...

Does something like this do what you want?

INSERT TABLEM(ItemId, jAmount)

SELECT t1.Item_Id, ISNULL(SUM(b.Var1), 0.00)

FROM table1 t1

JOIN table2 t2 ON t2.InventDimId = t1.InventDimId

AND t2.wmsLocationId 'The Room'

JOINbTable bON b.ItemId = t1.Item_Id

AND b.DataAreaId...

Makes no difference where the column is physically in the table.

Table can be Col1, Col2, Col3. You can retrieve them in any order you need/want/like.

EM won't "re-create" an index unless...

It gets out of whack pretty quick, I never depend on it (pardon the pun).

Google sp_msdependencies to see if it can be of use to you.

Appropriate indexing. If you see Bookmark Lookup in the plan, you may want to re-examine the indexes on the table.

Clustered index scans = table scan. You already know about these.

Stored...

SELECT OBJECT_NAME(id), name

FROM sysindexes

WHERE OBJECT_NAME(id) NOT LIKE'sys%'

AND indid > 0

AND indid < 255

ORDER BY 1, 2

Note: table functions where the result set table has an index will also...

Quite.

Thanks!

Perhaps you could explain what you mean about Death by SQL? IsNumeric is a system function with a single precise purpose. In my humble estimation, pattern matching (especially with NOT,...

IF IsNumeric(RIGHT(RTRIM('ABCDEF1234'), 4)) = 1

print 'yay'

else

print 'boo'

As already stated above, get the numbers and the letters into separate columns -- the way it's currently designed is not good, as evidenced...

Still had the old IP in SQL Client on the machine. D'Oh!

If you google SQL deadlock, you'll find a list of things to watch out for.

Top of the list:

1) Keep transactions as short as possible

2) Always access tables in same order,...

Absolutely put it in sproc.

And correct, the code to call it is

EXECUTE sproc_name

That code does not contain a subquery, therefore the error message refers to something else.

UPDATE

SET sent = 1

WHERE sent IS NULL

AND Received(?) < DATEADD(HOUR, -2, GETDATE())

Actually, I thought it was pretty clear that as much as possible should be in the DB. Those business rules that cannot be implemented as DRI should be coded into...