How to create exe from Perl files

Option 1: Use a Perl package such as PAR or PAR-Packer.
Assuming you have installed ActiveState ActivePerl, just go to command prompt and run the following:
ppm (launch perl package manager)
search (confirm the package available for download)
install

More info:
PAR-Packer: http://search.cpan.org/~rschupp/PAR-Packer-1.008/lib/pp.pm
example: pp -o packed.exe source.pl

Option 2: Use Perl2Exe.
http://www.indigostar.com/perl2exe.php
Download the version compatible with your Perl Installation and unzip the contents. Refer to the readme for more info.
Basically the command should just be perl2exe yourscriptname.pl

Option 3:
Use perlcc built-in command. I 'm not sure whether this works for Windows though.

web based administration for SQL server 2005

Purpose: a relatively fast and economical solution to administer SQL Server 2005 over the web. Ever heard of php myAdmin?

Main components needed in the host server:
- SQL Native Client
- Microsoft SQL Server 2005 Management Objects Collection* (optional)
- Microsoft SQL Server 2005 Backward Compatibility Components
- SQL Web Data Administrator (For my case I am using SQL Server 2005)

Both SQL Native Client and Microsoft SQL Server 2005 Management Objects Collection can be found from Microsoft Downloads: http://www.microsoft.com/downloads/en/details.aspx?familyid=DF0BA5AA-B4BD-4705-AA0A-B477BA72A9CB&displaylang=en

SQL Web Data Administrator is an open source project as of now; it is not officially supported by Microsoft. Use at your own risk!

Steps:
1. Download the required executables from Microsoft Library.
2. Download SqlWebAdmin source code from codeplex. Codeplex is an open source repository for .NET code. http://sqlwebadmin.codeplex.com/. Setup instructions can be found in the project site so I'm not going to elaborate.
3. Compile the source code locally if needed.
4. Install SQL Native Client (sqlncli.msi) and Microsoft SQL Server 2005 Backward Compatibility Components (SQLServer2005_BC.msi). For the latter, it is sufficient to pick SQL Distributed Management Objects (SQL-DMO) feature and disable all other features.

Alternatively, you can download the free lite version of myLittleAdmin at http://www.mylittletools.net/en/welcome.aspx

where can I find Oracle Client 9i?

Go to http://edelivery.oracle.com/EPD/Search/handle_go

Select the two check boxes and click on Continue.
In the next page select Oracle Database as Product Pack and pick OS.

Click Go for Searching.
in the result sheet, Click on 'Oracle9i Database Release 2 (9.2.0.1.0) Media Pack for Microsoft Windows'

Click download on for 'Oracle9i Client Release 2 (9.2.0.1.0) for Microsoft Windows 98/NT/2000/XP'

Lost installation product key?

Remote login to similar server and run regedit.
Locate the entries - it's probably under My Computer - HKEY_LOCAL_MACHINE - SOFTWARE
If you're lucky you might find the product key in the registry.

Named Pipes Provider, error: 40 - Could not open a connection to SQL Server

Reference: http://social.msdn.microsoft.com/Forums/en-US/sqldataaccess/thread/c488cf76-2515-440f-b3f8-9cfad689c5b6

The error is reported by client library. While your server is listeing on remote TCP, client will still try TCP and NP connection in order. So the error client behavior is expected. From what you have described, I believe that even though you enabled the remote TCP connection on the XPSP2 machine, you didn't make the TCP listening port an exception of XPSP2 personal firewall. You should follow steps below to resolve this issue.



1. check the SQL Server Errorlog to make sure SQL Server is now listening on TCP/IP and confirm which port it is listening on. Usually 1433. In the Errorlog, you will see several lines that discuss what SQL Server is listening on. Below is an example:

2006-01-04 01:41:07.65 server SQL server listening on 10.254.1.150: 1433. <--Shows the IP Address and the port.

2006-01-04 01:41:07.65 server SQL server listening on 127.0.0.1: 1433. <--Shows another IP Address and the port.

2006-01-04 01:41:07.69 server SQL server listening on TCP, Shared Memory, Named Pipes.

2006-01-04 01:41:07.69 server SQL Server is ready for client connections

2, Make sure on Windows XP that the firewall is not blocking that port.

3, go to your client machine and run the client network configuration tool (cliconfg.exe) Make sure TCP/IP is enabled, click properties and make sure the port number is the same one as SQL Server is listening on. Here you can enable NP or disable client NP as well.

Once both the client and the server are using TCP/IP with the same port number and the firewall on server machines is not blocked, you should be able to connect.