Tim's Computer Web Site

Installation of Microsoft SQL Server requires that it have certain permissions in order to run on the local system.  Some people choose to have it run under a Domain Account that has Administrative Access.  And at one point (especially SQL Server v6.5 and SQL Server v7.0) it was much easier to install if you used an Acount that had Administrative access (i.e., Local Administrator Group role).  I even believed at one point that using a Domain account made it easier for SQL Agent jobs to export data to remote file shares.

Sometimes you need to bind a second IP address to a Network Interface Card.  Maybe you need access to another network temporarily or you just need to fix something that comes with a default address not on your network.

From Linux, you can execute the following command:

ifconfig eth0:1 192.168.5.16 netmask 255.255.255.0 up

This will add a second IP Address to your eth0 network interface.

The appliance obtains its IP via DHCP. The virtual console will display it at the top of the screen:

Citadel virtual appliance - (C) 2007 http://www.citadel.org
To log in to Citadel, point your web browser to http://192.168.1.22

How do you tell if you're running on 32-bit or 64-bit hardware?

While the command uname -a will show wether you are using a 32-bit or 64-bit Operating System (as well as possibly looking at /etc/*release), it won't tell you if your hardware is actually 64-bit or not.

Murphy walks among us. You know Murphy, the famous "optimist" who helps make every bad situations even worse? Well, after a disaster has occurred is not the time to figure out how and where you need to recover your data. Sure, we practice (ok, hopefully we practice!) recovering our database(s) from tape or disk. And during our testing we restore it into a test database or, if we’re lucky enough, into a test server. Great, but how does the application connect to the recovered database if we’ve run into a massive hardware (server) failure?

The message of the day (motd) file is used by the System Administrators to display information to users when the log in to a system using a command line tool (for instance ssh).  On older systems, it was a single text file located in /etc/motd.  On Ubuntu, after around v10.10, it was changed to a series of scripts that are executed instead of simply displaying a text file.  There are many ways it can be invoked (or cause it to be displayed).

I had a problem when I copied a Linux virtual machine and made some changes (specifically which networks it could see on the host).  Specifically the ethernet devices changed and the udev process couldn't find the old devices, resulting in the network interfaces wouldn't come up.

For computers to talk on a network, they need a unique address.  The most common type of address is an Internet Protocol, or IP, address.  The address consists of a network portion and a device (computer) portion.  I use the term "device" only because it could be something other than a computer, like a printer.  It isn’t critical to understanding IP Addresses that there is a separate network portion and a separate device portion, but it does become important when you to want to understand how data moves across your personal network and across the internet.

There are a variety of ways to determine which version of SQL Server you are running. While the @@version information will tell you the current version
SELECT @@version
SELECT LTRIM(RIGHT(LEFT(@@VERSION,38),9))

The following code will as well, and in a slightly different format:
SELECT 'SQL Server '