Charles Kincaid (12/31/2010)

---

dforck (12/31/2010)

---

I find it amusing that he bothered to mention using char instead of varchar, but never mentioned that using nvarchar, or nchar, effectively doubles how much space...

@GrassHopper, yeah, making your tables a little leaner today doesn't save you that much disk space in the short term. However, there's a great advantage in the...

I find it amusing that he bothered to mention using char instead of varchar, but never mentioned that using nvarchar, or nchar, effectively doubles how much space is being used...

Ted Kreuger FTW!

could have been better if it would have had a better example of replaceing something with a set operation instead of a while loop. from what i've been told...

Seems like a good way to hide protions of a report from specific people, but i dont' understand why you would hide an entire report when you can just hide...

Microsoft isn't perfect, and no application is truely 100% complete. SP's save a lot of time (especially when updating fresh installs).

I agree on the 6-month sp then...

As far as i am aware and can tell it doesn't seem that you can share data sets. However, it is much easier to manage datasets by using stored...

try breaking up the move into chunks. so you'd first move rows 1-1000000, then 1000001 to 2000000 then 2000001 to 3000000 etc.

also, you might disable/remove any/all indexes until after...

why aren't you just using a single sp with a while loop? and then just call that sp from a job?

Well i figured it out. The stored procedure had a try-catch and transaction set up in it, so the errors we're reporting like they normally would. i copied...

ok, i'm confused. i know you can make a model in report manager, but lookign through visual studios i didn't see anything, and looking thorugh analysis services in management...

did you create the model in visual studios, or were you in report manager when you created it? or did you create it some other way?

did you publish the model to ssrs or create it in ssrs?

imo this is better (atleast easier to understand at a glance), performance should be the same if not better

select *

from tbl_activities

where

(

@key is null

or (@key is not null and...