From fuller.artful at gmail.com  Tue Nov 11 13:34:09 2014
From: fuller.artful at gmail.com (Arthur Fuller)
Date: Tue, 11 Nov 2014 14:34:09 -0500
Subject: [dba-SQLServer] UpgradeDB
Message-ID: <CAEPJO1i=MNk7FFh=pYMyWwY6-=Eu-xNqtDc3LYX7-oTU0nAXDw@mail.gmail.com>

Interesting article with code on CodeProject. The basic idea is this: a
team (small or large) is simultaneously developing new parts of the
database, and needs a way to integrate the changes and update the target
database. As always, the article includes the source code, and is
well-described in the piece.

http://www.codeproject.com/Articles/727970/UpgradeDB

-- 
Arthur

From accessd at shaw.ca  Wed Nov 12 11:30:23 2014
From: accessd at shaw.ca (Jim Lawrence)
Date: Wed, 12 Nov 2014 10:30:23 -0700 (MST)
Subject: [dba-SQLServer] UpgradeDB
In-Reply-To: <CAEPJO1i=MNk7FFh=pYMyWwY6-=Eu-xNqtDc3LYX7-oTU0nAXDw@mail.gmail.com>
Message-ID: <937498278.42250477.1415813423230.JavaMail.root@cds018>

It does seem that this application could be very useful. Being able to create self-contained easily transferable upgrade wizard packages would have helped in a number of previous projects.

Jim 

----- Original Message -----
From: "Arthur Fuller" <fuller.artful at gmail.com>
To: "Discussion concerning MS SQL Server" <dba-sqlserver at databaseadvisors.com>
Sent: Tuesday, November 11, 2014 11:34:09 AM
Subject: [dba-SQLServer] UpgradeDB

Interesting article with code on CodeProject. The basic idea is this: a
team (small or large) is simultaneously developing new parts of the
database, and needs a way to integrate the changes and update the target
database. As always, the article includes the source code, and is
well-described in the piece.

http://www.codeproject.com/Articles/727970/UpgradeDB

-- 
Arthur
_______________________________________________
dba-SQLServer mailing list
dba-SQLServer at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
http://www.databaseadvisors.com


From fuller.artful at gmail.com  Tue Nov 25 09:26:39 2014
From: fuller.artful at gmail.com (Arthur Fuller)
Date: Tue, 25 Nov 2014 10:26:39 -0500
Subject: [dba-SQLServer] Odds and evens
Message-ID: <CAEPJO1h+iD=c2cyMuJbNj=W9VFf19H=O-d6K2KTWy6V6MfdqNg@mail.gmail.com>

An app I'm currently sketching out needs to list addresses by street, but
with a kicker: I want to two groups per street -- odd and even street
numbers. Ultimately, the front end will present a list of streets, and let
the user select odd or even numbers, resulting in a list of those odd or
even addresses.

One idea I haven't really thought through yet would involve using the
modulus to distinguish the two groups, and then maybe build two views,
based on whether the modulus is 1 or 0. Then I could just swap the views,
depending on the user's choice of odd or even. In this scenario, the index
would be StreetName, Modulus(StreetNumber), or something like that

Any alternative suggestions?
-- 
Arthur

From gustav at cactus.dk  Tue Nov 25 09:47:34 2014
From: gustav at cactus.dk (Gustav Brock)
Date: Tue, 25 Nov 2014 15:47:34 +0000
Subject: [dba-SQLServer] Odds and evens
In-Reply-To: <CAEPJO1h+iD=c2cyMuJbNj=W9VFf19H=O-d6K2KTWy6V6MfdqNg@mail.gmail.com>
References: <CAEPJO1h+iD=c2cyMuJbNj=W9VFf19H=O-d6K2KTWy6V6MfdqNg@mail.gmail.com>
Message-ID: <4b8492e0e71649ebbcacee090bce64aa@AM2PR06MB0913.eurprd06.prod.outlook.com>

Hi Arthur

I don't think an index on Modulus(StreetNumber) will be of much use as you still will have to scan half the records of StreetName - and how many will these be? A couple of hundreds, max?

/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 16:27
Til: Discussion concerning MS SQL Server
Emne: [dba-SQLServer] Odds and evens

An app I'm currently sketching out needs to list addresses by street, but with a kicker: I want to two groups per street -- odd and even street numbers. Ultimately, the front end will present a list of streets, and let the user select odd or even numbers, resulting in a list of those odd or even addresses.

One idea I haven't really thought through yet would involve using the modulus to distinguish the two groups, and then maybe build two views, based on whether the modulus is 1 or 0. Then I could just swap the views, depending on the user's choice of odd or even. In this scenario, the index would be StreetName, Modulus(StreetNumber), or something like that

Any alternative suggestions?
--
Arthur



From fuller.artful at gmail.com  Tue Nov 25 10:23:28 2014
From: fuller.artful at gmail.com (Arthur Fuller)
Date: Tue, 25 Nov 2014 11:23:28 -0500
Subject: [dba-SQLServer] Odds and evens
In-Reply-To: <4b8492e0e71649ebbcacee090bce64aa@AM2PR06MB0913.eurprd06.prod.outlook.com>
References: <CAEPJO1h+iD=c2cyMuJbNj=W9VFf19H=O-d6K2KTWy6V6MfdqNg@mail.gmail.com>
	<4b8492e0e71649ebbcacee090bce64aa@AM2PR06MB0913.eurprd06.prod.outlook.com>
Message-ID: <CAEPJO1hRR0WSaxRcrGUhU4twYahFoUcQFPcRg-M3-iPWrcpwPA@mail.gmail.com>

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
?

From gustav at cactus.dk  Tue Nov 25 10:52:31 2014
From: gustav at cactus.dk (Gustav Brock)
Date: Tue, 25 Nov 2014 16:52:31 +0000
Subject: [dba-SQLServer] Odds and evens
Message-ID: <d8cc285445194803bd44df90f992d462@AM2PR06MB0913.eurprd06.prod.outlook.com>

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
? 



From ssharkins at gmail.com  Tue Nov 25 12:42:09 2014
From: ssharkins at gmail.com (Susan Harkins)
Date: Tue, 25 Nov 2014 13:42:09 -0500
Subject: [dba-SQLServer] Odds and evens
In-Reply-To: <CAEPJO1h+iD=c2cyMuJbNj=W9VFf19H=O-d6K2KTWy6V6MfdqNg@mail.gmail.com>
References: <CAEPJO1h+iD=c2cyMuJbNj=W9VFf19H=O-d6K2KTWy6V6MfdqNg@mail.gmail.com>
Message-ID: <CA++Sg+fijAwML8ryt-WnfNU97+UeAp9s0P82N1OTmVM6ZBhmKw@mail.gmail.com>

I don't think you need two views, just a procedure to pass the appropriate
filtering criteria.

Susan H.

On Tue, Nov 25, 2014 at 10:26 AM, Arthur Fuller <fuller.artful at gmail.com>
wrote:

> An app I'm currently sketching out needs to list addresses by street, but
> with a kicker: I want to two groups per street -- odd and even street
> numbers. Ultimately, the front end will present a list of streets, and let
> the user select odd or even numbers, resulting in a list of those odd or
> even addresses.
>
> One idea I haven't really thought through yet would involve using the
> modulus to distinguish the two groups, and then maybe build two views,
> based on whether the modulus is 1 or 0. Then I could just swap the views,
> depending on the user's choice of odd or even. In this scenario, the index
> would be StreetName, Modulus(StreetNumber), or something like that
>
> Any alternative suggestions?
> --
> Arthur
> _______________________________________________
> dba-SQLServer mailing list
> dba-SQLServer at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
> http://www.databaseadvisors.com
>
>

From fuller.artful at gmail.com  Tue Nov 25 13:33:03 2014
From: fuller.artful at gmail.com (Arthur Fuller)
Date: Tue, 25 Nov 2014 14:33:03 -0500
Subject: [dba-SQLServer] Odds and evens
In-Reply-To: <CA++Sg+fijAwML8ryt-WnfNU97+UeAp9s0P82N1OTmVM6ZBhmKw@mail.gmail.com>
References: <CAEPJO1h+iD=c2cyMuJbNj=W9VFf19H=O-d6K2KTWy6V6MfdqNg@mail.gmail.com>
	<CA++Sg+fijAwML8ryt-WnfNU97+UeAp9s0P82N1OTmVM6ZBhmKw@mail.gmail.com>
Message-ID: <CAEPJO1jrONrXbDQ4_JRkQZwaBTzZxe+sWsdaX3atUNkG=cUAGQ@mail.gmail.com>

Good point, Susan.

On Tue, Nov 25, 2014 at 1:42 PM, Susan Harkins <ssharkins at gmail.com> wrote:

> I don't think you need two views, just a procedure to pass the appropriate
> filtering criteria.
>
> Susan H.
>
>

From accessd at shaw.ca  Wed Nov 26 12:48:47 2014
From: accessd at shaw.ca (Jim Lawrence)
Date: Wed, 26 Nov 2014 11:48:47 -0700 (MST)
Subject: [dba-SQLServer] Odds and evens
In-Reply-To: <CAEPJO1hRR0WSaxRcrGUhU4twYahFoUcQFPcRg-M3-iPWrcpwPA@mail.gmail.com>
Message-ID: <1063717523.54847332.1417027727550.JavaMail.root@cds018>

Hi Arthur:

Built such a program many years ago and it was designed to assign a riding and poll code to every address record given a file with the legal description. It was a fairly slow process but computers and programs have improved dramatically since the early eighties. ;-) The program was good in that it could spit out a sorted poll list given the initial voters' lists. After an evening of canvassing the data could be easily updated and new unregistered constituents would automatically inserted. 

Maybe we should collaborate as 2015 promises to be an exciting year?

Jim  

----- Original Message -----
From: "Arthur Fuller" <fuller.artful at gmail.com>
To: "Discussion concerning MS SQL Server" <dba-sqlserver at databaseadvisors.com>
Sent: Tuesday, November 25, 2014 8:23:28 AM
Subject: 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
?
_______________________________________________
dba-SQLServer mailing list
dba-SQLServer at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
http://www.databaseadvisors.com



From jnatola at hotmail.com  Sun Nov 30 10:27:46 2014
From: jnatola at hotmail.com (J- P)
Date: Sun, 30 Nov 2014 11:27:46 -0500
Subject: [dba-SQLServer] sqlexpress upgrade
Message-ID: <BLU178-W27ED8202E7234961CE8F73BC7C0@phx.gbl>

Hi all, this is a 2 parter

1.) I have a sqlexpress 2005 database on a 2003 server, as 2003 is nearing EOL (as is the hardware ) i *THINK* perhaps this may be a good time to upgrade the DB to a newer version ? (any thoughts/suggestions )

Assuming I do upgrade to 2008r2 express, is it better to install a fresh 2008express and do  a restore of the database via SSMS, or install 2005express restore the DB, then install 2008 and let the wizard do the upgrade?

2.) There are a bunch of mtc routines amongst other things I'd like to keep/migrate to the new server, is it possible to restore the master DB to the new machine? if so is this recommended/advised?

**This is a production server so upgrading to 2008express  on the live server is not an option**

TIA,

J