Well, someone had to do it. The usergroup's been dead for over a year. Now I actually have some time to do stuff like this.

As an example:

select c.AccountNumber, soh.OrderDate, soh.SalesOrderNumber from Sales.Customer c

inner join Sales.SalesOrderHeader soh on c.CustomerID = soh.CustomerID

where SalesPersonID = 282 and c.TerritoryID = 6

select c.AccountNumber, soh.OrderDate, soh.SalesOrderNumber from Sales.Customer c...

jacob sebastian (10/7/2008)

---

JOIN clause is evaluated before WHERE is evaluated. If your query contains a number of joins, you might get better performance by moving the filter to the ON...

A restore creates the database exactly as it was at the time of backup, tables, indexes, etc. There's no rebuild necessary at all.

What you do need to do after upgrading...

What do you want explaining?

Is this for a demo or presentation or similar?

It's basically saying that you are asking for a single row to be deleted, but if it does the delete, two will go. To delete only one of duplicate set,...

zespri (10/6/2008)

---

Also in SQL Server Books Online it is stated :

This is not entirely correct. Two Serializable transactions...

My first suggestion would be to optimise the proc. Replace those cursors with set-based code that should run a lot faster. If you're doing cross tabs, look up the PIVOT...

Without indexes SQL has to do table scans and hence will take table-level locks. With appropriate indexes, SQL can take more granular locks and hence the two connections don't block...

What's it doing that it shouldn't be or not doing what it should?

Basically, can you give us a little more detail on what's wrong?

Again because of the varchar/nvarchar

In fn_get_sql, the text column is of type text, is a non-unicode value, so datalength returns the length of the string and hence dividing that by...

That should work.

Just one thing, you don't need the second if exists. Just put the update in the else part of the if.

As it's currently written, the second if exists...

Look at it as an opportunity. 😉

Try adding the indexes back after inserting the data but before querying it. If you're doing more than 1 or 2 queries, you may well see a large benefit.