Microsoft Windows Server 2003 R2 Enterprise Edition VHD

Logging into Microsoft Windows Server 2003 R2 Enterprise Edition VHD

I had to test a software under Microsoft Windows Server 2003 and I decided to download
the pre-configured for version of Microsoft Windows Server 2003 R2 Enterprise Edition VHD
for Microsoft Virtual Server. I've downloaded the files and started the Virtual Server
but I couldn't log in successfully with different passwords even with my current user's one (of the host
machine) did not work out.

I continued digging over the internet and I found this posing which gave me the information I need:

http://bink.nu/Article8737.bink

Credential Details

Administrator Password for Microsoft Windows Server 2003 R2 Enterprise Edition VHD

username: Administrator
password: Evaluation1

Related Resources

• Microsoft Windows Server 2003 R2 Enterprise Edition VHD
• Microsoft Virtual Server 2005 R2

Update

Login information can also be found in the ReadMe.htm file residing in the folder where installer has just extracted the files.

MS SQL Server vs Oracle

I was searching internet for MS SQL Server staff I found a very
useful site. Bristle Software made great feature comparison table comparing MS SQL Server and Oracle.

http://www.bristle.com/Tips/SQL.htm

SELECT VERSION in MS SQL Server

How to SELECT VERSION MS SQL Server

In order to select the version of MicroSoft SQL Server you may use following commands

SQL Command:

Select @@Version

Result:

Microsoft SQL Server 2000 - 8.00.194 (Intel X86) Aug 6 2000 00:57:48 Copyright (c) 1988-2000 Microsoft Corporation Developer Edition on Windows NT 5.1 (Build 2600: Service Pack 2)

SQL Command:

EXEC sp_MSgetversion

Result:

[8.00.194|1|3]

Note:
The last SQL command returns a row with 3 columns and "|" is used as separator.

MS SQL Server 2000 on Windows XP Pro

If you're not using a server operating system such as Windows 2000 Server or Windows 2003 Server you should consider using a developer edition of Microsoft SQL Server because Enterprise versions won't work for you (as stated in System Requirements).

1. Start the Installation.

2. Add program in firewall in "Programs and Services" list (for each instance if any) and
Enable SQL Server connectivity on Windows XP Service Pack 2

3. Start -> Programs -> Microsoft SQL Server -> Enterprise Manager to configure.

4. Configure Data Source Name
Data Source MUST be added in "System DSN" Data Sources in order
to be globally available because web server's user may differ from the currently logged one.

Start -> Control Panel -> Administrative Tools -> Data Sources (ODBC)
click on tab: ["System DSN"] Fill the Required Data

5. Perl Example

use DBI;
use CGI::Carp 'fatalsToBrowser';

my $DSN = 'driver={SQL Server};Server=DATABASE_SERVER_NAME;
database=MY_DATABASE_NAME;uid=MY_USER_NAME;pwd=MY_PASSWORD;';

$dbh = DBI->connect("dbi:ODBC:$DSN") or die($!);
print "Content-type: text/html\n\n";
print "Hi";

Save this example in a .pl or .cgi file in CGI enabled directory (usually cgi-bin) and execute it from your browser.
If you see the message "Hi" so we made it :)

Thanks for reading.

Pay attention to the details.

Intro

This week a had a task to work on a module that works on Microsoft SQL Server.
During the installation of Microsoft SQL Server 2005 on my Windows XP Professional
I saw a warning message concerning system requirements and they were not met ?!?
I thought that it is some how a minimal memory issue and I hit NEXT button.
The installation finished successfully so I was happy.

I installed version of Microsoft SQL Server 2005 and what will be the next step ?
The next step is the configuration. The default configuration of Microsoft SQL Server 2005
denies remote connections, this will be a server so we really need remote connections enabled.

Start -> Program -> Microsoft SQL Server 2005 -> Configuration Tools -> SQL Server Surface Area Configuration

I got following error message

No SQL Server 2005 components were found on the specified computer. Either no components are installed, or you are not an administrator on this computer. (SQLSAC)

How it's possible ?!?

Did you remember the warning message about the system requirements at install time ?
Now, I did.

The moral of this challenge is to pay attention even to small things and
not to ignore any warning/error message.

Thanks for reading.

Related

• MS SQL Server 2005 System Requirements
• http://www.datamasker.com/SSE2005_SAC.htm
• http://www.west-wind.com/WebLog/posts/4493.aspx