Koozie Notes

Issues Converting from SQL 7 to SQL 2005: 6.5 Compatibility

Yesterday evening, I was working on moving an old database from MS SQL Server 7.0 to a new server running MS SQL Server 2005.  Using SQL 2005 Management Studio, the moved database just stated "Database Name" (6.5 Compatibility).

After a few google searches, I found this site describing the same problem.  To correct the problem and convert the old database to SQL Server 2005 format, you would issue the following SQL command:

EXEC sp_dbcmptlevel 'MyDBName', '90';

I learned another fact last night about SQL 2005. SQL Enterprise manager, which was in SQL 2000 and SQL 7.0, is now called Management Studio. And the query analyzer, which used to be a separate application, is now incorporated inside SQL 2005 Management Studio.

--Chris

Old School Programing: Basic-256

While listening the Leo and Steve on the "Security Now!" podcast, they mentioned BASIC-256, a version of BASIC used to teach computer programming.  This evening, I downloaded and ran it.  Pretty cool. 

It reminds me of childhood programming on my Sinclair 1000, typing out programs, and saving them to cassette tape.

BASIC-256 web site.

You might also want to take a look at a Salon article title, "Why Johny Can't Code."

--Chris

Funky Error Code Using Perl and Win32::ODBC

While working on a perl script today, I came accross a strange error message from Win32::ODBC.

[Microsoft][ODBC Microsoft Access Driver] Too few parameters. Expected 1.

Now in the SQL statement, I was passing in the following VBA function:
    DateDiff( interval, date1, date2, [firstdayofweek], [firstweekofyear] )

When I passed in  DateDiff( "d", date1, date2), I received an error.  So I left off the double quotes and passed in DateDiff( d, date1, date2), which still failed.

Solution:  Pass it in with single quotes.

DateDiff( 'd', date1, date2)

--Chris