Re: Odd text encoding

2015-09-12 Thread Stephen Price
et.com [mailto: > ozdotnet-boun...@ozdotnet.com] *On Behalf Of *Bec C > *Sent:* Friday, 11 September 2015 4:59 PM > > > *To:* ozDotNet > *Subject:* Re: Odd text encoding > > > > I get your point Ken but is power really increasing at such a rate? > > On Friday,

RE: Odd text encoding

2015-09-11 Thread Ken Schaefer
going to get faster and faster over time. From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On Behalf Of Bec C Sent: Friday, 11 September 2015 4:59 PM To: ozDotNet Subject: Re: Odd text encoding I get your point Ken but is power really increasing at such a rate? On

Re: Odd text encoding

2015-09-11 Thread 罗格雷格博士
Ah but the issue is how many rows you can write into a table. That's a bit more work than a for loop :-) Regards Greg Dr Greg Low SQL Down Under +61 419201410 1300SQLSQL (1300775775) On 11 Sep 2015, at 5:16 pm, Greg Keogh mailto:gfke...@gmail.com>> wrote: Assuming computing power doubles eve

Re: Odd text encoding

2015-09-11 Thread Greg Keogh
> > Assuming computing power doubles every 18-24 months, then that 5444 years >> will become a lot less, relatively quickly. >> > I didn't mention that counting to 2^63 is eminently parallelizable, so lets divide up a small fraction of the free internet computing power on the problem and see how lo

Re: Odd text encoding

2015-09-10 Thread Bec C
en that 5444 years > will become a lot less, relatively quickly. > > > > *From:* ozdotnet-boun...@ozdotnet.com > [mailto: > ozdotnet-boun...@ozdotnet.com > ] *On > Behalf Of *Greg Keogh > *Sent:* Friday, 11 September 2015 10:15 AM > *To:* ozDotNet > > *Subj

RE: Odd text encoding

2015-09-10 Thread Ken Schaefer
Greg Keogh Sent: Friday, 11 September 2015 10:15 AM To: ozDotNet Subject: Re: Odd text encoding but because they were concerned about the possibility of running out of bigint values. (Clearly it’s a pity more maths isn’t taught at schools). My PC can do a for int loop up to 2^30 in about 20

RE: Odd text encoding

2015-09-10 Thread Ken Schaefer
:00 PM To: ozDotNet Subject: Re: Odd text encoding >> it's usually more secure to store as base64 oh god not again. base64 is just a representation of the data in printable ASCII characters. - think binary (base2), hex (base8) :) base64 has absolutely nothing to do with security.

Re: Odd text encoding

2015-09-10 Thread Thomas Koster
On 10 September 2015 at 22:09, David Rhys Jones wrote: > Database performance, high critical databases it's faster to write text than > binary, this might have changed with the last version of SQL but it was true > up until '2008 Binary data is naturally faster to copy and compare than text becau

RE: Odd text encoding

2015-09-10 Thread 罗格雷格博士
t-boun...@ozdotnet.com] On Behalf Of Greg Keogh Sent: Friday, 11 September 2015 10:15 AM To: ozDotNet Subject: Re: Odd text encoding but because they were concerned about the possibility of running out of bigint values. (Clearly it’s a pity more maths isn’t taught at schools). My PC can do a for int l

Re: Odd text encoding

2015-09-10 Thread Greg Keogh
> > but because they were concerned about the possibility of running out of > bigint values. (Clearly it’s a pity more maths isn’t taught at schools). > My PC can do a for int loop up to 2^30 in about 20 seconds. To get to 2^63 non-stop it will take 5444 years -- *GK*

RE: Odd text encoding

2015-09-10 Thread 罗格雷格博士
om] On Behalf Of Greg Keogh Sent: Thursday, 10 September 2015 10:12 PM To: ozDotNet Subject: Re: Odd text encoding i think ive read it somewhere, a rule of thumb is if you dont need to do calculations with your "number", make it a string In 2006 where I was working they created a new SQL DB

Re: Odd text encoding

2015-09-10 Thread Greg Harris
Oh Yeah! Friday rant to follow... >From my experience there usually is no good reason for this sort of thing. I've seen people attempt to store phone numbers as a number and surely most here have seen similar things. >Yea the phone number thing *facepalm* >ask them how they gonna store 000 as num

Re: Odd text encoding

2015-09-10 Thread 罗格雷格博士
; I'll just have to add a base64 decode function and I should be fine. >>>> >>>> Regards, >>>> >>>> Greg >>>> >>>> Dr Greg Low >>>> >>>> 1300SQLSQL (1300 775 775) office | +61 419201410 &

Re: Odd text encoding

2015-09-10 Thread Greg Keogh
> > i think ive read it somewhere, a rule of thumb is if you dont need to do > calculations with your "number", make it a string > In 2006 where I was working they created a new SQL DB and the natural key of the most important table was a 12 digit number (customer number I think) and there were arg

Re: Odd text encoding

2015-09-10 Thread David Rhys Jones
pm, Stephen Price >> wrote: >> >>> >> >>> How did you get my Azure certificate? wtf?? >> >>> >> >>> Seriously though, the trailing == on the end (plus the overall look) >> makes >> >>> it look exactly like an A

Re: Odd text encoding

2015-09-10 Thread Nelson
t look exactly like an Azure publish certificate. >> >> >> >>> On Thu, 10 Sep 2015 at 08:39 Greg Low (罗格雷格博士) >> wrote: >> >>> >> >>> Perfect thanks Thomas. >> >>> >> >>> I'll just have to add

Re: Odd text encoding

2015-09-10 Thread DotNet Dude
> >>> > >>> I'll just have to add a base64 decode function and I should be fine. > >>> > >>> Regards, > >>> > >>> Greg > >>> > >>> Dr Greg Low > >>> > >>> 1300SQLSQL (1300 775 775)

Re: Odd text encoding

2015-09-10 Thread Nelson
he trailing == on the end (plus the overall look) > makes > >>> it look exactly like an Azure publish certificate. > >>> > >>>> On Thu, 10 Sep 2015 at 08:39 Greg Low (罗格雷格博士) > wrote: > >>>> > >>>> Perfect thanks Th

Re: Odd text encoding

2015-09-10 Thread Davy Jones
015 at 08:39 Greg Low (罗格雷格博士) wrote: >>>> >>>> Perfect thanks Thomas. >>>> >>>> I'll just have to add a base64 decode function and I should be fine. >>>> >>>> Regards, >>>> >>>> Greg >>>&

Re: Odd text encoding

2015-09-10 Thread 罗格雷格博士
gt;>> 1300SQLSQL (1300 775 775) office | +61 419201410 mobile│ +61 3 8676 4913 >>> fax >>> SQL Down Under | Web: www.sqldownunder.com >>> >>> -Original Message- >>> From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com]

Re: Odd text encoding

2015-09-10 Thread Mark Hurd
gt; >>> 1300SQLSQL (1300 775 775) office | +61 419201410 mobile│ +61 3 8676 4913 >>> fax >>> SQL Down Under | Web: www.sqldownunder.com >>> >>> -Original Message- >>> From: ozdotnet-boun...@ozdotnet.com >>> [mailto:ozdotnet-boun...@ozdo

Re: Odd text encoding

2015-09-10 Thread Thomas Koster
> SQL Down Under | Web: www.sqldownunder.com >> >> -Original Message- >> From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] >> On Behalf Of Thomas Koster >> Sent: Thursday, 10 September 2015 10:33 AM >> To: ozDotNet >> Subject:

Re: Odd text encoding

2015-09-09 Thread 罗格雷格博士
m> -Original Message- From: ozdotnet-boun...@ozdotnet.com<mailto:ozdotnet-boun...@ozdotnet.com> [mailto:ozdotnet-boun...@ozdotnet.com<mailto:ozdotnet-boun...@ozdotnet.com>] On Behalf Of Thomas Koster Sent: Thursday, 10 September 2015 10:33 AM To: ozDotNet mailto:ozdotnet@ozdotnet.

Re: Odd text encoding

2015-09-09 Thread Nelson
nunder.com >> >> -Original Message- >> From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] >> On Behalf Of Thomas Koster >> Sent: Thursday, 10 September 2015 10:33 AM >> To: ozDotNet >> Subject: Re: Odd text encoding >>

Re: Odd text encoding

2015-09-09 Thread Stephen Price
..@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] > On Behalf Of Thomas Koster > Sent: Thursday, 10 September 2015 10:33 AM > To: ozDotNet > Subject: Re: Odd text encoding > > On 10 September 2015 at 10:21, Greg Low (罗格雷格博士) wrote: > > This one’s driving me crazy

RE: Odd text encoding

2015-09-09 Thread 罗格雷格博士
-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On Behalf Of Thomas Koster Sent: Thursday, 10 September 2015 10:33 AM To: ozDotNet Subject: Re: Odd text encoding On 10 September 2015 at 10:21, Greg Low (罗格雷格博士) wrote: > This one’s driving me crazy and I thought the brains trust might ha

Re: Odd text encoding

2015-09-09 Thread Thomas Koster
On 10 September 2015 at 10:21, Greg Low (罗格雷格博士) wrote: > This one’s driving me crazy and I thought the brains trust might have an > idea. > > Here’s a value that’s stored in an ntext column in a SQL Server DB: > H4sIAAAEALVW0W7aMBT9lanvre0wBkNtJEo3DWkFBGGvyDiXYi22M9vpYL/Wh33SfmGGJASatKOS95KH3

RE: Odd text encoding

2015-09-09 Thread 罗格雷格博士
et.com [mailto:ozdotnet-boun...@ozdotnet.com] On Behalf Of Greg Low (??) Sent: Thursday, 10 September 2015 10:21 AM To: ozDotNet Subject: Odd text encoding Hi Folks, This one’s driving me crazy and I thought the brains trust might have an idea. Here’s a value that’s stored in an ntext column in a SQL

Odd text encoding

2015-09-09 Thread 罗格雷格博士
Hi Folks, This one’s driving me crazy and I thought the brains trust might have an idea. Here’s a value that’s stored in an ntext column in a SQL Server DB: H4sIAAAEALVW0W7aMBT9lanvre0wBkNtJEo3DWkFBGGvyDiXYi22M9vpYL/Wh33SfmGGJASatKOS95KH3HvPyTk+tvPn6fe1NLg3Bas5PMIsS0H3GVOZtJGm0lBmuZJfuLFKb99