Totally agree with Doug. FOR XML PATH *is* the way to solve these problems in SQL Server 2005. Now, that said I will vote *against* doing such thing on the...

global temporary tables (##) DO get dropped automatically when ALL the connections that reference them are CLOSED.

You can find that here

For convenience this is the relevant part:

...

Global temporary tables have...

We do it all the time but computing fragmetation level is paramount if you have to do it intraday 😉

If you created the clustered index in the new file you effecively moved the table to that file. 😉

DBCC SHOW_STATISTICS

sdhan79 (2/4/2008)

---

Thank you noeld!! can I ask you one more???

If I am understanding this right, your query sample will look for

any customer who made purchase between given periods (let...

sdhan79 (2/4/2008)

---

Hi, first of all, thanks for reading my first post :).

I am currently trying to create a query to find the number of active customers on each month.

Business rule...

The "right" way is to put the calculated column in an inline view so that you have access to the name in the outer query. Oh and No it does...

Indexed View 😉 ... any one ?

I believe the real problem lies in this part:

Queries of views are "VERY" deceiving and indexes may not be appropriately used because you are hiding...

Totally in favor of using BCP over that "30000" insert lines !!!!

it is absolutely valid to cast the text column as xml

select x.vakue('Xpath Expression', 'datatype') extractedXmlData

from (

select cast( txtcol as xml) x from table

) data

One second is too short of a latency. The best you could do is to reduce the "ppoling interval" to one second but that will be "pushing" it ...

I vote for that 😀

given that you have only two drives I doubt that separating tables in different filegroups is going to buy you anything in terms of "preformance". Recovery time is probably a...