You are here: Re: Relationships error, C# Visual Studio 2005 database bug?, "the columns in table XYZ do not match an existing primary key or UNIQUE constraint", copying columns « MsSQL Server « IT news, forums, messages
Re: Relationships error, C# Visual Studio 2005 database bug?, "the columns in table XYZ do not match an existing primary key or UNIQUE constraint", copying columns

Posted by SQL Menace on 07/15/07 13:06

On Jul 15, 8:34 am, raylopez99 <raylope...@yahoo.com> wrote:
> On Jul 15, 5:15 am, SQL Menace <denis.g...@gmail.com> wrote:
>
> > Also how will you do one of these queries
> > return all customers who live in LA and have ordered product x between
> > June 2006 and July 2007
>
> > Denis The SQL Menace
>
> You wrote your dB is 300 GB--but how much of this is raw data?
> Perhaps 10%? The other 90% is junk to link the data (I'm guessing).
> If so, you can buy 30 GB of RAM and when x86/Windows supports 64 bit
> better (though I think they already do--Itanium?) you can access this
> 30 GB with no problem. 30 GB RAM costs about $1000. Not expensive.
>
> As for the query: " > return all customers who live in LA and have
> ordered product x between > June 2006 and July 2007"
>
> This is simple using a flat file as I propose: "customers & (order*
> or purchase or buy*) & product x & (DATE T (June 2006 < T < July
> 2007))". Suitable code can be written to make these Boolean operators
> work. Some cleanup might be required to strip out false hits, but
> these false hits are present in regular databases today. Also
> remember right now with RDBMS you expend a tremendous amount of work
> putting data into "orthogonal" databases, via data entry forms. You
> have to pay people to enter the data correctly (even if your program
> rejects bad data entry, you still have to pay people to enter the data
> correctly). You can avoid all of this with a flat file. Just dump
> the raw data into memory and let an inference or search engine index
> the data and make the associations via pointers.
>
> RL

>>You wrote your dB is 300 GB--but how much of this is raw data?
Perhaps 10%? The other 90% is junk to link the data (I'm guessing).
If so, you can buy 30 GB of RAM and when x86/Windows supports 64 bit
better (though I think they already do--Itanium?) you can access this
30 GB with no problem. 30 GB RAM costs about $1000. Not expensive.

No junk my friend, the data goes back to May 1896 so yes it is 300GB,
the junk (as you call it) is maybe 10 MB (probably a lot less, these
are the lookup tables)
BTW this is just 1 DB We have several of these on the server

Now for a more interesting question. Ever heard of SOX? How would you
do your audit trail?


Denis The SQL Menace
http://sqlservercode.blogspot.com
http://sqlblog.com/blogs/denis_gobo/default.aspx

 

Navigation:

[Reply to this message]


Удаленная работа для программистов  •  Как заработать на Google AdSense  •  England, UK  •  статьи на английском  •  PHP MySQL CMS Apache Oscommerce  •  Online Business Knowledge Base  •  DVD MP3 AVI MP4 players codecs conversion help
Home  •  Search  •  Site Map  •  Set as Homepage  •  Add to Favourites

Copyright © 2005-2006 Powered by Custom PHP Programming

Сайт изготовлен в Студии Валентина Петручека
изготовление и поддержка веб-сайтов, разработка программного обеспечения, поисковая оптимизация