Lesson for today

[sobrique]

In SQL.
"SELECT INTO" will clobber what was in the table originally.
This means it's not a good idea if you've just spent half an hour populating that table already.

Grr.

Oh well, at least I still have the source data and translation scripts.

Comments

[necessitysslave.livejournal.com]

been there done that spent 4 hours sorting out the mistake

[xarrion.livejournal.com]

learning the difference between SELECT INTO and INSERT INTO is one most people learn the hard way ;)

[sobrique.livejournal.com]

I just did.
Thankfully the contents of that table were mostly populated from a spreadsheet that I still had (and so just had to hack together the SQL again).

[xarrion.livejournal.com]

isn't SQL joyous :)
I've been teaching our gas team the wonders of SQL* recently.


*also called 'Access would take 3 hours to run that query. Do it my way.'.

[sobrique.livejournal.com]

Annoyingly I'm having to use SQL server 2000, rather than Oracle. (Licensing, features reasons - the app wants to use something that you don't get without oracle enterprise, despite the fact that SQL Server doesn't have that feature)

[xarrion.livejournal.com]

hehe. Although from my occasional forays into MSDN, it appears that SQL Server has its own set of features independent of SQL, and likes using a sliiightly different terminology too.
The reason for the team having problems at the moment is that the Microsoft ODBC drivers really, really don't play nice with Oracle package views.

[warmage.livejournal.com]

...and are slow like molasses in january to boot.