Well, as Michael Weiss pointed out, you can archive your OLAP database, take the file, move it to another server and restore from there. If your database is too large,...

In addition, just by doing Copy and Paste (see popup menu) you can copy an entire Analysis Services database (cubes, dimensions, etc.) to a different server, then process it there...

Here are all the functions that might be of any use in this case. I do not think those will help to accomplish your goal. You ned to capture the...

Here are a few points.

1. To find a process that blocked the given one you can run

sp_who2 Active

It will show the blocking process id in the BlkBy column. However...

You need to use your own if the following example is not what you need:

select convert( char, $3133845.54, 1 )

Michael

Tim, it was a nice try, very creative.

Michael

Tim, you DO put WHERE clause before the JOIN (in a way):

SELECT ...

FROM t1

JOIN t2

ON t1.c1 = @value

AND t1.c2 = t2.c2

As far as letting your developers to select "everything"...

Tim, I do avoid views because there is not a reason to use those in most cases. The downside of views is that optimizer is not always capable of creating...

Well said.

I usually fight (well, almost) to receive precise requirements on what kinds of reports users will need to generate. "Report on anything in any combination, shape and form" cannot work....

This is not ugly. One recommendation I would make is to use stored procedures instead of views. Views do not support parameters while stored procedures do. Therefore I do not...

Try to deal with a view in the same manner you deal with a table either in stored procedure or in VB (ADO). It does not matter (especially if the...

The suggested solution is good but use #tmp_Table instead of tmp_Table.

Depending on the application design and needs, you could also return the entire resultset to the front end and break...

If the table is inserted into once a month only, it is not your bottleneck. Nevetheless, you could use a proper fillfactor to avoid page splits (say, 85%). After each...

This will work well if TableA is not extremely large. Also consider that NOT IN does not work "as might be expected" if there is a NULL value in the...