[dba-VB] Merge rows

Shamil,

It is easy to say that but I am a single proprietor.  If I do something that I don't charge then i 
lose my billable time.  If I do something that doesn't work then do I bill the customer?  Etc.

Maybe for an hour's work but what about a week's work?

I will likely do things like this over time.  Test out the process on a portion of the database. 
Learn to use this method.  But I am pretty fully booked as it is, with paying work.  More efficient 
is good, EASY more efficient is VERY GOOD.  Difficult more efficient may not be good at all.

It's a balancing act.

John W. Colby
www.ColbyConsulting.com


Shamil Salakhetdinov wrote:
> John,
> 
> OK, someday you can make it working/flying using C# with your current DB
> size "shrinked" ~8 times and your current processing time shortened X times
> (to an order of magnitude? - wild guess)...
> 
> ... but do not wait until you'll get fluent with C# - it's time consuming as
> everybody's experience shows - and it's not needed to get the outlined above
> results - just do it - how to do it seems to be clear now?...
> 
> --
> Shamil
> 
> -----Original Message-----
> From: dba-vb-bounces at databaseadvisors.com
> [mailto:dba-vb-bounces at databaseadvisors.com] On Behalf Of jwcolby
> Sent: Wednesday, September 23, 2009 12:25 AM
> To: Discussion concerning Visual Basic and related programming issues.
> Subject: Re: [dba-VB] Merge rows
> 
> Shamil,
> 
> You are asking the wrong guy on this stuff.  I am not fluent in SQL Server,
> even with all that I do.
> 
> Eventually I will be moving everything I can to c#, once I am fluent in c#.
> For now I use stored 
> procedures for all of the actual order processing.
> 
> The whole bit mask thing will definitely be "someday", with a big MAYBE.
> 
> John W. Colby
> www.ColbyConsulting.com