[dba-SQLServer] Odds and evens

Hi Arthur

Yes, I'm familiar with the process, though not the organizing of it. I'm sure you can add some tools for streamlining the task.

/gustav

-----Oprindelig meddelelse-----
Fra: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] På vegne af Arthur Fuller
Sendt: 25. november 2014 17:23
Til: Discussion concerning MS SQL Server
Emne: Re: [dba-SQLServer] Odds and evens

Good point, Gustav. At most, I think there would be only about 1000 numbers on any given street. I didn't mention it, but this is for an app to be used by canvassers for a political party. (In case you're unfamiliar with that term, a canvasser goes door to door and invites the occupant to vote for their candidate; if they are supporters, would they like a sign for their lawn or window, etc.) Typically, a pair of canvassers will work together, each on one side of the street. Hence the need for two lists per street.
The electoral units are called (in Canada) ridings; each riding will ultimately elect one candidate, and that candidate will end up with a seat in Parliament.

Ridings have completely arbitrary definitions. A street may easily span several ridings; hence the need for an upper and lower street number for each street within a given riding. But yes, as you guessed there may well be only a few hundred rows per street, so there's really no need to index the street numbers. The query itself will easily handle that many records.

Arthur
​