I would not say expert but in 2008 you don't use asmx for web service if you are not using IIS for your deployment, check below for howyou create your...

There are some fixed things you must do that is a copy of your datasource database must be running in production so all you have to do is copy your...

You could enable Named Pipes and TCP/IP which is what I do but you also have the option to use NetMon to see how your Named Pipes are opened and...

Do you see any issue with this behavior? It looks like a client made a NP connection to the server after the Pipe is created, but before it's ready to...

That is very good question because...

You could use SQL Server 2005 you just need to create model which can run from View, Table and some queries and some is the operative word because Table and...

Yes you could there are Express binaries that installs in WOW64 only problem Express comes without the Agent so you may have to use x86 scheduling in your x86 directory...

Actually I don't think much code is needed what is needed in 2005 is to create the models, if you are in the planning stage a better option is to...

If you have Visual Studio running you may already have SQL Server Express running connect your x86 package to it and move Oracle data into it and then move it...

You could try 9i RC2 client because most development with Oracle and Microsoft platform Oracle binaries are created to work with 9i client instead of 8i. So you need...

If I understand you correctly you need to rerun setup and choose repair and choose components then choose all because you may need all.

You must be missing something a SQL Server database comes as MDF and LDF or .BAKs which could be in .zip or .rar or MSI files but not PDF file....

This error generally means SSRS have dropped your connection credentials so open your report in BIDs and edit the connection property and add the connection credentials.

I have covered that error in the thread below.

http://www.sqlservercentral.com/Forums/Topic686672-146-1.aspx#bm687570

That error means you are in x64 server so if you are in Win2003 you need to install SP2 which will install the x86 ODBC and if you are in...