What's the difference between saving a null and a zero

[ryandoah]

Hi All,

I sent some DB design specs to our "DB" guy. In the specs are some fields that may or may not have values inserted into them, ie; if data is supplied for a field it is inserted, if not, no insertion to that field. I had sent the spec stating that several of the fields were to allow nulls, since I didn't know if they would have data supplied to them or not. Our "DB" guy decided it would be more efficient to not allow nulls into any of the values, overriding me and opting to give them a default value of zero. This kind of erks me for several reasons. First, being a Comp Science BA graduate, I fully understand the difference between what a zero is and what a null is, thus I set this up to allow nulls for fields that may not have any info, not ones that have have zero info. Secondly, I was under the assumption that a zero took more space to save than a null, in SQL Server, granted not much individually, but possibly a great bit on the large scale. Am I wrong? What is the size difference between saving a null and a zero? Also, if the data type is Currency, wouldn't it make since to have the default save as 0.00, than just plain 0? Or am I just being nitpicky.

Thanks,
ryandoah

 

[ryandoah]

I agree, Catadmin, I'm just trying to get a good work record, post collegiate graduation, so I don't look like a job hopper. Though nothing in my previous work history would suggest such.

I read an article not long ago that suggested that for every year that an IT professional spent in an enviroment that was non condusive to professional development, they lost a 1/4 of their professional effectiveness. This due to the speed with which the technology advances.

FYI, they are still using SQL7 here. The job I spent 2 years at actually learning my trade was using SQL2000. There was a year gap between these 2 jobs, as I quit working to finish school.

 

[vongrunt]

I read an article not long ago that suggested that for every year that an IT professional spent in an enviroment that was non condusive to professional development, they lost a 1/4 of their professional effectiveness. This due to the speed with which the technology advances.

More likely because of frustration. Technology advances, but technology fundamentals are pretty much the same since 70's. From that perspective, difference between SQL7 and SQL2000 is trivial.

------
Math problems? Call 0800-[(10x)(13i)^2]-[sin(xy)/2.362x]

 

[Catadmin]

And now you have another problem. SQL 2005 is coming out this year so you may have to learn your technical skills all over again, depending on what changes MS has made to the program.

I can tell you know, though, that I hate SQL Reporting Services. I hope they've fixed it in the SQL 2k5 release so you don't have to go back and cleanup all the problems the report designer creates. I much prefer Crystal because of that problem.



Catadmin - MCDBA, MCSA
Beware the error of pre-emptive poultry inventory!

 

[ryandoah]

vongrunt, you are correct, so far that I have found, there is little difference between SQL7 and SQL2000, with the exception of a few minor features that ease development. The principles are pretty much the same, so I guess that is a bit of a moot point.

 

[ryandoah]

Oops, didn't mean to submit yet.

The point being is that while SQL7 still may do the job properly, it is none the less a 10 year old piece of software, which is considered well out of date. And I think not having any experience in the newer versions may make me less marketable once I do decide to continue my career elsewhere.

 

[r937]

learn a skill that you can use in any database environment

like data modelling

sounds like you'd be pretty good at it, too

rudy | r937.com | Ask the Expert | Premium SQL Articles
SQL for Database-Driven Web Sites (next course starts May 8 2005)

 

[Catadmin]

Don't forget that many database developers have trial version software that you can download. I know MS did on the SQL Server 2000 and probably will on SQL Server 2k5. Get a cheap computer with the minimum necessary specs, download a trial version of a Server OS along with the trial of the DB software and have fun playing with it and trying to break it.

That's a fantastic way of keeping up your skills. And you can even put it in your resume as freelance Contracting work. I did. "Installed and Administered SQL Server in SOHO test environment..."

Recruiters do count it as long as you do it honestly and can say you learned something from it. @=)



Catadmin - MCDBA, MCSA
Beware the error of pre-emptive poultry inventory!