Something to start with.

if object_id('tempdb..#Items')is not null drop table #Items

CREATE TABLE #Items(

[ID] [int] NOT NULL, -- FK to another table

[int] NOT NULL,

[BEGIN] [int] NOT NULL, -- I think this...

I've done something similar, however it was just to view the contents. The problem you will find is the 1000 record limit on pulling data from AD. I also didn't...

How about this?

if object_id('tempdb..#chartemp')is not null drop table #chartemp

create table #chartemp(

charcol nvarchar(15) )

insert into #chartemp

values ('''DA''=''T*''')

select charcol from #chartemp

Is there something I'm missing that won't allow you to do the following?

set nocount on

go

begin try

begin transaction

declare @counter int

set @counter = 0

while @counter < (select count(id) + 1 from

(

select...

If you grab SQL Prompt, you can use the snippets. Makes things really smooth.

If you are like me and can't seem to convince someone to pay for that software, I'd...

Perhaps, using EXEC will help you solve this. What I would suggest is something like the following:

DECLARE @sToolVersion NVARCHAR(55)

DECLARE @sqlStatement varchar(1000)

SET @sToolVersion = (SELECT tool_pref_value

...

Great! I think using a date table / dimension may work for you on this. Check out the following article:

http://www.sqlservercentral.com/scripts/Data+Warehousing/65762/

It's not really specific to Data Warehousing. It works really great...

Oscar, I think I am following what you are trying to accomplish. Let me know if I am correct.

There is an agreement regarding overtime. This agreement is a compilation of...

I think you will find this link very interesting. I didn't follow everything you were doing in your TSQL, but I think this may help.

http://stackoverflow.com/questions/585645/calculating-different-tariff-periods-for-a-call-in-sql-server

Let me know if I'm off...

You'd put something like the following into your field.

="Report for dates between " & DateAdd("M",-12,Parameters!startdate.Value) & " and " & Parameters!startdate.Value

Thanks, Paul. I have a long way to go. And you guys make it a whole lot easier.

If I understand data types correctly (that's a huge assumption) then it doesn't really matter what the length is set to, nvarchar(max) would be exactly the same size (in bytes)...

Thanks for the idea, I will look into that as well. I was hoping that by working with data I had, and knew about, that it would be somewhat...

Outstanding, that's exactly what I am looking for, thank you very much.

Alright, I have no idea if the data I created is representative of what you have. After playing for a bit, I think it's a simple bit of changing this...