Steven Wright Blog

I have managed to set-up a SQL Server 2005 Express instance, on a windows-XP machine, with remote connections enable. The actual installation of the SQL Server 2005 express instance was straightforward, but enabling the remote connections was problematic. I found that I was not the only person. In the end I found these steps worked for me: Open up the SQL Server Surface Area Configuration Manager Click on Surface Area configurations for services and connections. Click the remote Connections entry on the tree, select local and remote connections (TCP/IP) . Click OK. Open the SQL Server Configuration Manager Select SQL Server 2005 Network Configuration/Protocols for the instance. Right click TCP/IP, select properties. Click the IP Addresses tab, change the Enable flag on the IP addresses to YES. In the IPAll section, copy the port value of the TCP Dynamic Ports to the TCP Port. Clear the TCP Dynamic Port value. Click Okay. Open up Control Panel/Firewall. Click Exception

Do you need to write a custom component to transform input data, and disregard this input data, instead, replacing it? That's was what I needed to accomplish with my component. It takes data from the input buffer and performs a lookup via an external API. If there is a match, send the result data down a "match" output otherwise send the input data down a "unmatch" output. The key here is that the "shape" of the output was changing. In other words, the metadata of the output was very different from that of the input.I also want my component to be synchronous (meaning synchronous, I mean that the component takes a row, processes it and then immediately sends it down an output) and not asynchronous (meaning that it reads all the data and then processes the data in an internal buffer). Now from what I was reading and seeing this was what I thought SSIS meant by synchronous and asynchronous components, but I was wrong! An asynchronous component can either

I am currently working on a project which needs to load over a 1000 xml files. The files are stored across 10 subfolders. I am using a foreach loop with a file enumerator, which is configured at the top of the folder structure and traverses the subfolders. This loops through the files, load the data and then moves the file to another folder. The package executes fine for a few 100 files but then hangs; this happens after a different number of processed files each time the package is run. While trying to resolve the problem we ran performance counters and noticed that the number open handles increased significantly just about the time Dtexec looked like it had hanged and DTexec also then started taking a lot of the cpu processing time. Update: I put this on the Microsoft forums and got a intresting answer back See Here ; There seems to be a memory leak with foreach loop which should be fixed in sp1.