smknox (5/17/2009)

---

It seems like my simplest option might be to pull lots of records over the network (one sp without a where clause) and then filter out what I want...

smknox, you have 2 options here.

1. Proceed with multiple stored procedures. But you need to make the application to choose which one to call basing on what's selected in the...

I guess it would be easier if you'd provide the requirements to this code. Describe what this code actually should...

karthikeyan (5/15/2009)

---

Hi All,

I have one scenario.

declare @mm char(2)

declare @gdate datetime

select @gdate = '03/31/2009'

select @mm = convert(char(2),datepart(month,@gdate))

select @mm

It is showing 3. But i need the output as 03.

I modified the...

CHECKSUM is not good enough.

Different records may have the same CHECKSUM.

When 2 are betting one of them is a fool, another one is a...

John (5/8/2009)

---

Normalization is awesome! But considering this is a 'flattened' out table for a 'reporting' data mart it was deemed necessary for 'denormalize' the information for performance reasons. Thanks for...

Try again.

Here is a shorter version of your code, easier to get:

DECLARE @Fixed2 decimal(8,4)

SET @Fixed2 = 12121.03

jbraunstein (5/7/2009)

---

1. Extra zeros to the right of a decimal point are ignored so 100.0 and 10.000 are the same. If the variable is cast as a float or decimal,...

That's how the function should look like:

CREATE FUNCTION AdversePartiesForRequest

(@RequestID int)

RETURNS nvarchar(4000)

AS

BEGIN

declare @AdverseParties nvarchar(4000)

SELECT @AdverseParties = ISNULL(@AdverseParties+ ', ', '') + AdverseParty

FROM dbo.AdverseParty

WHERE @RequestID = RequestID

ORDER BY ??? -- if you...

Search this forum for "Concatenation Function".

Create scalar function to accept RequestID and return all corresponding "AdverseParty" values concatenated in one string.

Then you may call it like this:

SELECT R.RequestID. R.Name, dbo.AdversPartForRequest(R.RequestID)...

Always use FLOAT data type for complex calculations.

DECLARE @Hundred float

SET @Hundred = 100

Update #temp

set gross = (((1.0+(week1/@Hundred))*

(1.0+(week2/@Hundred))*

(1.0+(week3/@Hundred)))-1)*@Hundred

Just make sure you have updates statistics before you query for RowCnt from sysindexes.

It does not reflect real number of records all the time.

Another way to go would be creating system procedure in master database.

Then you just call that procedure from any of databases and get results relevant to that particular database.

Here is...

Then you need to make some effort in...