Okay, I feel even smaller now with all this praise. Jeff, the last word most people at work would use to describe me is humble. At work, yes,...

GilaMonster (3/2/2008)

---

Lynn Pettis (2/29/2008)

---

Since you would ask about Statistics in an interview, what can do you look for in an answer? I have been working with MS SQL Server...

You won't. You are rounding to the 100ths...

Jack Corbett (2/29/2008)

---

Lynn Pettis (2/29/2008)

---

Jeff,

Okay, sorta helps, but still I'm not quite there. Does that shoot me down from working with you or do I at least understand enough...

Jeff,

Okay, sorta helps, but still I'm not quite there. Does that shoot me down from working with you or do I at least understand enough that they are used...

Gail,

Since you would ask about Statistics in an interview, what can do you look for in an answer? I have been working with MS SQL Server since 1996/1997 (6.5/7.0/2000/2005)...

Jeff Moden (2/29/2008)

---

Lynn Pettis (2/29/2008)

---

Jeff, I'll give you an "It depends". Yes, it is the start date of the current record, and it with the StatuteId does uniquely identify...

The only thing I remember regarding booleans in Access is that -1 is a true value and zero is false. Based on that, wouldn't that mean you just need...

here is a slight variation to what Michael Valentine Jones provided:

declare @year smallint,

@month tinyint

set @year = 2007

set @month = 2

select

...

Jeff, I'll give you an "It depends". Yes, it is the start date of the current record, and it with the StatuteId does uniquely identify a single record. ...

Okay, I came up with a solution that should work in SQL 2000:

set nocount on

create table dbo.StatuteHistory (

StatuteId int,

WeightEffectiveDate datetime,

...

Mattie,

In SQL 2000, I'd probably add the WeightEndEffectiveDate field and use an insert trigger to update this field. The query then would select the records where the WeightEndEffectiveDate was...

Jeff,

Could you do it in SQL 2000 with a tally table and derived tables?

😎

Here is my updated code:

set nocount on

create table dbo.StatuteHistory (

StatuteId int,

WeightEffectiveDate datetime,

Weight int,

primary key...

You could also do something like this in SQL Server 2005/2008:

set nocount on

create table dbo.StatuteHistory (

StatuteId int,

WeightEffectiveDate datetime,

Weight...