CFUnited 2008:
Calendar
| Sun | Mon | Tue | Wed | Thu | Fri | Sat |
|---|---|---|---|---|---|---|
| 1 | 2 | 3 | ||||
| 4 | 5 | 6 | 7 | 8 | 9 | 10 |
| 11 | 12 | 13 | 14 | 15 | 16 | 17 |
| 18 | 19 | 20 | 21 | 22 | 23 | 24 |
| 25 | 26 | 27 | 28 | 29 | 30 | 31 |
Recent Entries
Come On In, Rails-The Water's Warm
Shan's Simple Examples: File uploads with Flex and ColdFusion
Recent Comments
Google Calendar API - Creating a new Calendar with ColdFusion
Steve Julian said: When and where are you going to post the finished CFC's ? Thanks
[more]
Three Phases of Programmer Development
Pat Branley said: I normally think of those phase 2 people as 'programmers' and the phase 3 people as 'developers'.
I...
[more]
New Job Title: Front End Engineer
Sean Corfield said: Well, there's always the excellent Fusion Authority Quarterly Journal...
[more]
Down To The Wire: HTTP Sniffers
Brian M said: I second the mention of the Charles Web Debugging Proxy that Tariq mentioned. It is fantastic. It s...
[more]
New Job Title: Front End Engineer
Patrick said: Heya Sean. Good point. I never understood how they did things over there at SysCon, and I understand...
[more]
Archives By Subject
Business of Software (4) [RSS]
ColdFusion (318) [RSS]
Conferences (6) [RSS]
Databases (87) [RSS]
Flex & Flash (109) [RSS]
Fusebox (87) [RSS]
General Development (29) [RSS]
Google (9) [RSS]
Hardware (5) [RSS]
JVM & Java (132) [RSS]
Linux (20) [RSS]
Miscellaneous (254) [RSS]
Performance (8) [RSS]
SeeFusion (36) [RSS]
Shan's Simple Examples (7) [RSS]
User Interface (3) [RSS]
Windows (5) [RSS]
Archives By Poster
Daryl Banttari (10)
Nat Papovich (29)
Patrick Quinn (36)
Shannon Hicks (22)
Steve Nelson (21)
Tyson Vanek (3)
Running SQL Server 2000 and 2005 side-by-side
There's a copious quantity of information online about running MSSQL2k and MSSQL2k5 at the same time, but I just did it, and wanted to document my process.
First off, you must have SP4 installed on SQL Server 2000. (I'm running the MSDE edition.) Additionally, you have to have that version installed before installing 2005. (I'm using the Developer not Express edition.) MSSQL 2000 will be accessed using the default (non-named) instance, and MSSQL 2005 will use a named instance. (I chose MSSQL2005 as the instance name.)
I'm something of a stickler for keeping my data files outside of my program files directory ever since suffering a major system failure a while back. With data files on a separate drive, it's easier to run system backups of my data once a day, while reserving backups of my entire c: drive for every-now-and-then. I didn't want to have to make a setup.ini file for the SQL Server 2005 install just to move the data directory and I especially didn't like what I read in the docs about how the installer configures the data directory location. (I.e. inside a couple directories deep, like "MSSQL.1\MSSQL\Data" if you just change the data directory during install.)
But it's easy enough to install MSSQL 2005 in a next-next-next defaults kinda way and change both the default location for new data files and move the existing system data files to a different location.
You'll need to follow these instructions from Microsoft on moving the system databases. And to set the default data directory, just change it via the Database Settings node from the System Properties screen from within SQL Server Management Studio (the new Enterprise Manager).
So that's all there is to it. If you want to make a ColdFusion DSN to a SQL Server named instance, you enter the server like this: "LOCALHOST\INSTANCE_NAME", so in my case, it was "tanto\mssql2005".
Don't forget to update SQL Server to Service Pack 2. It's slower than snot to install, but who knows what kind of buffer overflows will be found in the RTM?
