Thursday, March 31, 2011

SQL Server 2008 and ColdFusion 9: no problems, right?

Sure, once it's set up. lol.

ColdFusion and SQL Server talk to each other very well, except when they don't. In a development environment, like, say, your laptop, they don't talk at all by design: CF wants to connect via TCP/IP and SQL Server ships with TCP/IP disabled by default.

So, thanks to Adobe help, Ben Forta's post, and Marc Esher's post, I got it working ...

  • Follow the instructions in Esher's post above to open TCP/IP services in your SQL Server instance (enable TCP/IP, click on Properties, IP Addresses, delete all Dynamic Port values, and enter 1433 as the TCP Port, assuming you do have it running on 1433).
  • Follow the instructions in Forta's post as well (enable Windows and SQL Server authentication, create a SQL Server account for ColdFusion[1], and give it access to the database in question).
  • In the CF Administrator, enter the username and password for the SQL Server account you just created[2], leave the server name blank, and enter the name of the database to which you want to connect.

That's everything, I think, although I probably skipped over some of the painful details. Anyway, it's more complicated than it should be, and it's not all on Microsoft: there are plenty of JDBC connectors that don't have this issue. Adobe just hasn't improved their built-in connector.


[1] Unless, of course, you already have ColdFusion running under a separate user account, which is good, in which case you simply let CF log in using Windows Authentication. (return)

[2] Username and password are required only for SQL Server authentication; for Windows authentication, neither are required (because the user is already logged in). (return)

Friday, March 11, 2011

That's the end of that

Last season, Purdue struggled without Robbie Hummel in the lineup. They pulled out an 8-point win over Northwestern in the first round, but then took a 40-minute dump against Minnesota in the semis.

This year, the dump came one round earlier. While fellow possible #2 seeds Duke and Syracuse were playing tight games, Purdue failed to show up against Michigan State. The resulting loss not only secured the Spartans' spot in the tournament, but will likely drop Purdue to the bottom of the #3 line, hoping not to get pushed into a #4. (Now the Syracuse-Connecticut game needs to go the other way; the Huskies seem the most likely team to move up to a #3.)

It also begs the question of the chances that Purdue has to make a run this season. Gone is the glow from knocking off Ohio State and Wisconsin in the same week; in its place is the uncertainty brought on by losing to two second-division conference opponents in one week.

Matt Painter has his work cut out for him. He needs to get the problems fixed in practice the next few days, or one of the better teams in Purdue history is going to join some of its peers in the Disappointments section of the history books.

Purdue's #1 seed chances, Friday update

Recap from yesterday: no big surprises. Louisville crushed Marquette, so that sets up a semifinal matchup with Notre Dame that pretty much requires Purdue to reach the BTT finals. Looking at today's games:

  • Purdue has to beat Michigan State, or else the rest is moot.
  • A Duke loss to Maryland would be nice.
  • A BYU loss to New Mexico would be even better; anything that prevents a BYU-San Diego State matchup in the Mountain West Finals is a good thing. (The winner could end up in front of Purdue no matter which one it is.)
  • Connecticut is the team to support in the Big East. The winner of the Louisville-Notre Dame game will also be closing in on that fourth #1 seed.

Looking at the other side of the coin, North Carolina is up against a hot Miami team, but a team that just played a game last night. It's hard to tell exactly when that extra fatigue kicks in, but it could be tonight. San Diego State has only UNLV between themselves and a probable date with BYU; unfortunately for them, they're playing in Las Vegas. Florida plays Bruce "Dead Man Walking" Pearl's Tennessee squad, so despite possible consequences I'm rooting for Florida. (They're one of the three SEC schools that doesn't oversign in football – Florida, that is – so that's another good thing.) Texas plays archrival Texas A&M, and that might be just the type of game to end their Big 12 tournament run before it really starts.

No change from yesterday: a realistic seed for Purdue is the top #2; a worst-case scenario is the third #4. Updates to come later.

Thursday, March 10, 2011

Purdue's #1 seed chances, Thursday update

Purdue's road loss to Iowa dropped them from a solid contender for a #1 seed to a possible #3 or even #4, depending on what happens in Indianapolis. Bracketology 101 currently has them as the last #2 seed, but they've still got a chance at a top seed if a number of things go right.

  • Purdue must win the Big Ten tournament, most likely by beating Ohio State. It would help if they also beat Wisconsin so that they get two more top-20 RPI wins rather than just one. Doing it by beating, say, Penn State and Michigan will not help their position as much.
  • Duke needs to lose in the ACC tournament, preferably not to North Carolina, who is right behind Purdue. If UNC wins out, they could conceivably pass the Boilers even if Purdue also wins out.
  • BYU probably needs to lose once – none of their opponents, other than San Diego State, will do anything to help their SOS, and the loss of Davies may affect their seeding even if they do win the Mountain West. Their narrow escape against TCU today probably didn't help their cause.
  • The Big East tournament needs to break properly. Notre Dame can't win it, because that will probably solidify their #1 seed. (Pittsburgh's loss probably didn't matter; they're reportedly a solid #1.) Syracuse can't win it, because that will likely keep them ahead of Purdue due to the strength of their conference. (Syracuse beat St. John's in the quarters; Purdue will draw Michigan State or RPI dud Iowa.) Unfortunately they're in different brackets, so Purdue fans need to root for Connecticut and the Louisville/Marquette winner (but see below).

If Purdue doesn't win the conference tournament, then they probably can't keep their seed unless their loss is to Wisconsin or Ohio State, and even then, they'll need North Carolina to lose at a comparable time. San Diego State can't win the WAC, especially if it means beating BYU. The Aztecs are in a shaky position but simply don't have many losses, and a marquee win might get them past Purdue if the Boilers don't also get one. Florida can't win the SEC: even though it's a weak conference this year, it's not like the tournament champion is going to drop a seed or two. Texas probably shouldn't win the Big 12, either.

Louisville could become a problem, especially if they knock out both Marquette and Notre Dame. That could get them by a Purdue team with a quarterfinal loss; if the Cardinals win the Big East, that might get them by anything but a conference champion Boiler team. Wisconsin is in a similar position: unlikely to come near Purdue unless Purdue nosedives or Wisconsin wins the conference tournament (which would probably mean a win over Purdue). St. John's is out (guess the refs worked the whole game this time), and Kentucky may be too far back to pass the Boilers even if the Wildcats win the SEC.

For now, a realistic seed for Purdue is the top #2; a worst-case scenario is the third #4. Updates to come later.
There was an error in this gadget