Unix Technical Forum

SEO

vBulletin Search Engine Optimization


Go Back   Unix Technical Forum > Database Server Software > Microsoft SQL Server > SQL Server

Register FAQ Members List Calendar Search Today's Posts Mark Forums Read
  #1 (permalink)  
Old 03-01-2008, 11:33 AM
Twobridge
 
Posts: n/a
Default Actuarial sql statement Need Help.

I hope someone can help me out with my problem.
I have found a sql statement that basically pulls all bills filed
within a
certain time period and the payments made on those bills with in the
same time period. I group the payments by payment year and filed year
which gives me a matrix with the filed year as the row and the pay
year
as the column....and this appears fine. My problem is that my employer

does not want to see the payment year as the column header. He would
like to see the number of months from the bill year in sequence of 12
months periods. Also I have run into a problem that if I narrow down
my search to display only bills from a certain department. We may have

a instance where that department will not have any payments for that
time period.
My employer would like to see a zero in that spot on the matrix. My
sql statement
would simply skip that year and display the next years value. Any
suggestions? Someone else suggested the ISNULL but since there are no
payments for that year there would be no null to replace. This is a
sample of how they want it displayed

12 24 36
1985 $50 $100 $200
1986 $0 $120 $40
1987 $0 $0 $500

Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #2 (permalink)  
Old 03-01-2008, 11:33 AM
Erland Sommarskog
 
Posts: n/a
Default Re: Actuarial sql statement Need Help.

Twobridge (Twobridge@gmail.com) writes:
> I hope someone can help me out with my problem.
> I have found a sql statement that basically pulls all bills filed
> within a
> certain time period and the payments made on those bills with in the
> same time period. I group the payments by payment year and filed year
> which gives me a matrix with the filed year as the row and the pay
> year
> as the column....and this appears fine. My problem is that my employer
>
> does not want to see the payment year as the column header. He would
> like to see the number of months from the bill year in sequence of 12
> months periods.


The column names in a query are fixed, so you would just name the columns
12, 24, 36 etc.

Sorry, that is not a very good answer, but not knowing your query or
anything it's the best I can say.

> Also I have run into a problem that if I narrow down
> my search to display only bills from a certain department. We may have
>
> a instance where that department will not have any payments for that
> time period.
> My employer would like to see a zero in that spot on the matrix. My
> sql statement
> would simply skip that year and display the next years value. Any
> suggestions? Someone else suggested the ISNULL but since there are no
> payments for that year there would be no null to replace. This is a
> sample of how they want it displayed
>
> 12 24 36
> 1985 $50 $100 $200
> 1986 $0 $120 $40
> 1987 $0 $0 $500


Set up a one-column table with the years (or just get them from the
base table as (SELECT DISTINCT year FROM tbl) in a derived table.
The left join that table with the rest.

Here is a query from Northwind to illustrate:

SELECT m.month, nooforders = coalesce(o.cnt, 0)
FROM (SELECT DISTINCT month = convert(char(6), OrderDate, 112)
FROM Orders) AS m
LEFT JOIN (SELECT month = convert(char(6), OrderDate, 112),
cnt = COUNT(*)
FROM Orders
WHERE CustomerID = 'BERGS'
GROUP BY convert(char(6), OrderDate, 112)) AS o
ON m.month = o.month

--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #3 (permalink)  
Old 03-01-2008, 11:34 AM
Twobridge
 
Posts: n/a
Default Re: Actuarial sql statement Need Help.

I apologize for not getting back to you sooner, I do appreciate your
help. My database tables look like this

Bill Table
- billNumber
- fileDate

Transaction Table
- billNumber
- payDate
- amount

Currently I am trying this sql statement

SELECT SUM(Transaction.amount) AS [Amount Paid],
YEAR(Bill.fileDate) AS [Date Filed], YEAR(Transaction.payDate) AS
[Year Paid]
FROM Bill LEFT OUTER JOIN
Transaction ON Bill.billNumber =
Transaction.billNumber
GROUP BY YEAR(Bill.fileDate), YEAR(Transaction.payDate)
HAVING (YEAR(Bill.fileDate) BETWEEN 1985 AND 1990) AND
(YEAR(Transaction.payDate) BETWEEN 1985 AND 1990)
ORDER BY YEAR(Bill.fileDate), YEAR(Transaction.payDate)

You mentioned just simply naming the columns, the problem with that
solution is that the number of columns are different each
time...depending on the user query. My user can query by year. In the
statement I currently just hard coded in a year to test.


Erland Sommarskog wrote:
> Twobridge (Twobridge@gmail.com) writes:
> > I hope someone can help me out with my problem.
> > I have found a sql statement that basically pulls all bills filed
> > within a
> > certain time period and the payments made on those bills with in the
> > same time period. I group the payments by payment year and filed year
> > which gives me a matrix with the filed year as the row and the pay
> > year
> > as the column....and this appears fine. My problem is that my employer
> >
> > does not want to see the payment year as the column header. He would
> > like to see the number of months from the bill year in sequence of 12
> > months periods.

>
> The column names in a query are fixed, so you would just name the columns
> 12, 24, 36 etc.
>
> Sorry, that is not a very good answer, but not knowing your query or
> anything it's the best I can say.
>
> > Also I have run into a problem that if I narrow down
> > my search to display only bills from a certain department. We may have
> >
> > a instance where that department will not have any payments for that
> > time period.
> > My employer would like to see a zero in that spot on the matrix. My
> > sql statement
> > would simply skip that year and display the next years value. Any
> > suggestions? Someone else suggested the ISNULL but since there are no
> > payments for that year there would be no null to replace. This is a
> > sample of how they want it displayed
> >
> > 12 24 36
> > 1985 $50 $100 $200
> > 1986 $0 $120 $40
> > 1987 $0 $0 $500

>
> Set up a one-column table with the years (or just get them from the
> base table as (SELECT DISTINCT year FROM tbl) in a derived table.
> The left join that table with the rest.
>
> Here is a query from Northwind to illustrate:
>
> SELECT m.month, nooforders = coalesce(o.cnt, 0)
> FROM (SELECT DISTINCT month = convert(char(6), OrderDate, 112)
> FROM Orders) AS m
> LEFT JOIN (SELECT month = convert(char(6), OrderDate, 112),
> cnt = COUNT(*)
> FROM Orders
> WHERE CustomerID = 'BERGS'
> GROUP BY convert(char(6), OrderDate, 112)) AS o
> ON m.month = o.month
>
> --
> Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
>
> Books Online for SQL Server 2005 at
> http://www.microsoft.com/technet/pro...ads/books.mspx
> Books Online for SQL Server 2000 at
> http://www.microsoft.com/sql/prodinf...ons/books.mspx


Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #4 (permalink)  
Old 03-01-2008, 11:34 AM
Twobridge
 
Posts: n/a
Default Re: Actuarial sql statement Need Help.

I have found a way to generate the number for the columns by using
datediff(month, bill.fileDate, transaction.payDate)/ 12 * 12 and I
simply do a order by.....my problem now is when a payment is made
before a 12 month marker. This causes the datediff to return a 0/12 *
12 causing my report to produce a "0" column. I will be working on it
some more ...i will keep to up on any progress that i make.

Twobridge wrote:
> I apologize for not getting back to you sooner, I do appreciate your
> help. My database tables look like this
>
> Bill Table
> - billNumber
> - fileDate
>
> Transaction Table
> - billNumber
> - payDate
> - amount
>
> Currently I am trying this sql statement
>
> SELECT SUM(Transaction.amount) AS [Amount Paid],
> YEAR(Bill.fileDate) AS [Date Filed], YEAR(Transaction.payDate) AS
> [Year Paid]
> FROM Bill LEFT OUTER JOIN
> Transaction ON Bill.billNumber =
> Transaction.billNumber
> GROUP BY YEAR(Bill.fileDate), YEAR(Transaction.payDate)
> HAVING (YEAR(Bill.fileDate) BETWEEN 1985 AND 1990) AND
> (YEAR(Transaction.payDate) BETWEEN 1985 AND 1990)
> ORDER BY YEAR(Bill.fileDate), YEAR(Transaction.payDate)
>
> You mentioned just simply naming the columns, the problem with that
> solution is that the number of columns are different each
> time...depending on the user query. My user can query by year. In the
> statement I currently just hard coded in a year to test.
>
>
> Erland Sommarskog wrote:
> > Twobridge (Twobridge@gmail.com) writes:
> > > I hope someone can help me out with my problem.
> > > I have found a sql statement that basically pulls all bills filed
> > > within a
> > > certain time period and the payments made on those bills with in the
> > > same time period. I group the payments by payment year and filed year
> > > which gives me a matrix with the filed year as the row and the pay
> > > year
> > > as the column....and this appears fine. My problem is that my employer
> > >
> > > does not want to see the payment year as the column header. He would
> > > like to see the number of months from the bill year in sequence of 12
> > > months periods.

> >
> > The column names in a query are fixed, so you would just name the columns
> > 12, 24, 36 etc.
> >
> > Sorry, that is not a very good answer, but not knowing your query or
> > anything it's the best I can say.
> >
> > > Also I have run into a problem that if I narrow down
> > > my search to display only bills from a certain department. We may have
> > >
> > > a instance where that department will not have any payments for that
> > > time period.
> > > My employer would like to see a zero in that spot on the matrix. My
> > > sql statement
> > > would simply skip that year and display the next years value. Any
> > > suggestions? Someone else suggested the ISNULL but since there are no
> > > payments for that year there would be no null to replace. This is a
> > > sample of how they want it displayed
> > >
> > > 12 24 36
> > > 1985 $50 $100 $200
> > > 1986 $0 $120 $40
> > > 1987 $0 $0 $500

> >
> > Set up a one-column table with the years (or just get them from the
> > base table as (SELECT DISTINCT year FROM tbl) in a derived table.
> > The left join that table with the rest.
> >
> > Here is a query from Northwind to illustrate:
> >
> > SELECT m.month, nooforders = coalesce(o.cnt, 0)
> > FROM (SELECT DISTINCT month = convert(char(6), OrderDate, 112)
> > FROM Orders) AS m
> > LEFT JOIN (SELECT month = convert(char(6), OrderDate, 112),
> > cnt = COUNT(*)
> > FROM Orders
> > WHERE CustomerID = 'BERGS'
> > GROUP BY convert(char(6), OrderDate, 112)) AS o
> > ON m.month = o.month
> >
> > --
> > Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
> >
> > Books Online for SQL Server 2005 at
> > http://www.microsoft.com/technet/pro...ads/books.mspx
> > Books Online for SQL Server 2000 at
> > http://www.microsoft.com/sql/prodinf...ons/books.mspx


Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #5 (permalink)  
Old 03-01-2008, 11:34 AM
Twobridge
 
Posts: n/a
Default Re: Actuarial sql statement Need Help.

Sorry let me clarify....if a bill's file date is 1/1/1985 and is paid
on 3/3/1985 this causes the datediff function to produce a 3/12 * 12 in
my problem.....3/ 12 = 0 * 12....so now my column heading has a value
of 0 when in reality it should be grouped as a payment made in the
first 12 months. I hope this makes since.


Twobridge wrote:
> I have found a way to generate the number for the columns by using
> datediff(month, bill.fileDate, transaction.payDate)/ 12 * 12 and I
> simply do a order by.....my problem now is when a payment is made
> before a 12 month marker. This causes the datediff to return a 0/12 *
> 12 causing my report to produce a "0" column. I will be working on it
> some more ...i will keep to up on any progress that i make.
>
> Twobridge wrote:
> > I apologize for not getting back to you sooner, I do appreciate your
> > help. My database tables look like this
> >
> > Bill Table
> > - billNumber
> > - fileDate
> >
> > Transaction Table
> > - billNumber
> > - payDate
> > - amount
> >
> > Currently I am trying this sql statement
> >
> > SELECT SUM(Transaction.amount) AS [Amount Paid],
> > YEAR(Bill.fileDate) AS [Date Filed], YEAR(Transaction.payDate) AS
> > [Year Paid]
> > FROM Bill LEFT OUTER JOIN
> > Transaction ON Bill.billNumber =
> > Transaction.billNumber
> > GROUP BY YEAR(Bill.fileDate), YEAR(Transaction.payDate)
> > HAVING (YEAR(Bill.fileDate) BETWEEN 1985 AND 1990) AND
> > (YEAR(Transaction.payDate) BETWEEN 1985 AND 1990)
> > ORDER BY YEAR(Bill.fileDate), YEAR(Transaction.payDate)
> >
> > You mentioned just simply naming the columns, the problem with that
> > solution is that the number of columns are different each
> > time...depending on the user query. My user can query by year. In the
> > statement I currently just hard coded in a year to test.
> >
> >
> > Erland Sommarskog wrote:
> > > Twobridge (Twobridge@gmail.com) writes:
> > > > I hope someone can help me out with my problem.
> > > > I have found a sql statement that basically pulls all bills filed
> > > > within a
> > > > certain time period and the payments made on those bills with in the
> > > > same time period. I group the payments by payment year and filed year
> > > > which gives me a matrix with the filed year as the row and the pay
> > > > year
> > > > as the column....and this appears fine. My problem is that my employer
> > > >
> > > > does not want to see the payment year as the column header. He would
> > > > like to see the number of months from the bill year in sequence of 12
> > > > months periods.
> > >
> > > The column names in a query are fixed, so you would just name the columns
> > > 12, 24, 36 etc.
> > >
> > > Sorry, that is not a very good answer, but not knowing your query or
> > > anything it's the best I can say.
> > >
> > > > Also I have run into a problem that if I narrow down
> > > > my search to display only bills from a certain department. We may have
> > > >
> > > > a instance where that department will not have any payments for that
> > > > time period.
> > > > My employer would like to see a zero in that spot on the matrix. My
> > > > sql statement
> > > > would simply skip that year and display the next years value. Any
> > > > suggestions? Someone else suggested the ISNULL but since there are no
> > > > payments for that year there would be no null to replace. This is a
> > > > sample of how they want it displayed
> > > >
> > > > 12 24 36
> > > > 1985 $50 $100 $200
> > > > 1986 $0 $120 $40
> > > > 1987 $0 $0 $500
> > >
> > > Set up a one-column table with the years (or just get them from the
> > > base table as (SELECT DISTINCT year FROM tbl) in a derived table.
> > > The left join that table with the rest.
> > >
> > > Here is a query from Northwind to illustrate:
> > >
> > > SELECT m.month, nooforders = coalesce(o.cnt, 0)
> > > FROM (SELECT DISTINCT month = convert(char(6), OrderDate, 112)
> > > FROM Orders) AS m
> > > LEFT JOIN (SELECT month = convert(char(6), OrderDate, 112),
> > > cnt = COUNT(*)
> > > FROM Orders
> > > WHERE CustomerID = 'BERGS'
> > > GROUP BY convert(char(6), OrderDate, 112)) AS o
> > > ON m.month = o.month
> > >
> > > --
> > > Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
> > >
> > > Books Online for SQL Server 2005 at
> > > http://www.microsoft.com/technet/pro...ads/books.mspx
> > > Books Online for SQL Server 2000 at
> > > http://www.microsoft.com/sql/prodinf...ons/books.mspx


Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #6 (permalink)  
Old 03-01-2008, 11:34 AM
Erland Sommarskog
 
Posts: n/a
Default Re: Actuarial sql statement Need Help.

Twobridge (Twobridge@gmail.com) writes:
> I apologize for not getting back to you sooner, I do appreciate your
> help. My database tables look like this
>
> Bill Table
> - billNumber
> - fileDate
>
> Transaction Table
> - billNumber
> - payDate
> - amount
>
> Currently I am trying this sql statement
>
> SELECT SUM(Transaction.amount) AS [Amount Paid],
> YEAR(Bill.fileDate) AS [Date Filed], YEAR(Transaction.payDate) AS
> [Year Paid]
> FROM Bill LEFT OUTER JOIN
> Transaction ON Bill.billNumber =
> Transaction.billNumber
> GROUP BY YEAR(Bill.fileDate), YEAR(Transaction.payDate)
> HAVING (YEAR(Bill.fileDate) BETWEEN 1985 AND 1990) AND
> (YEAR(Transaction.payDate) BETWEEN 1985 AND 1990)
> ORDER BY YEAR(Bill.fileDate), YEAR(Transaction.payDate)
>
> You mentioned just simply naming the columns, the problem with that
> solution is that the number of columns are different each
> time...depending on the user query. My user can query by year. In the
> statement I currently just hard coded in a year to test.


If the number of columns or the column names are different depending
on user input, the query must be constructed dynamically. A query in
SQL returns a fixed number of columns with fixed names. This because
SELECT returns a table, and a table is supposed to describe an entity
with a fixed set of attributues.

Since it appears that you want to run a crosstab, you should have a look
at RAC, a third-party which is good for that sort of things. See
http://www.rac4sql.com/.

> Sorry let me clarify....if a bill's file date is 1/1/1985 and is paid
> on 3/3/1985 this causes the datediff function to produce a 3/12 * 12 in
> my problem.....3/ 12 = 0 * 12....so now my column heading has a value
> of 0 when in reality it should be grouped as a payment made in the
> first 12 months. I hope this makes since.


I'm afraid that I did not understand much. It seems that you have not
decided what output your query should give in this case, and this is
nothing we can assist you with in a newsgroup.

--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #7 (permalink)  
Old 03-01-2008, 11:35 AM
Ed Murphy
 
Posts: n/a
Default Re: Actuarial sql statement Need Help.

Erland Sommarskog wrote:

> Twobridge (Twobridge@gmail.com) writes:


>> Sorry let me clarify....if a bill's file date is 1/1/1985 and is paid
>> on 3/3/1985 this causes the datediff function to produce a 3/12 * 12 in
>> my problem.....3/ 12 = 0 * 12....so now my column heading has a value
>> of 0 when in reality it should be grouped as a payment made in the
>> first 12 months. I hope this makes since.


> I'm afraid that I did not understand much. It seems that you have not
> decided what output your query should give in this case, and this is
> nothing we can assist you with in a newsgroup.


Surely "first 12 months" ought to be followed by "second 12 months"
etc., and so
datediff(month, bill.fileDate, transaction.payDate)/ 12 * 12
should be changed to
(datediff(month, bill.fileDate, transaction.payDate)+11)/ 12 * 12
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
Reply


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On
Forum Jump


All times are GMT. The time now is 03:14 PM.


Powered by vBulletin® Version 3.6.5
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
SEO by vBSEO 3.2.0
UnixAdminTalk.com

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616