Any reason you don't want to use SSIS?

I think that error is related to files not being where the setup program is expecting them to be. Not sure about 2008, but on prior versions of SQL...

One way to do it:

On your original insert, add an identity field to your bulk table. That's very important, because that's the only think that will keep the rows...

Do you have any kind of table structure or are you trying to use SQL Server like an Excel spreadsheet? Based on the table data you provided, it looks...

Please take a look at How to post data/code on a forum to get the best help By Jeff Moden[/url].

Give an example of some queries you're running against the data and it would be much easier to get an understanding of what improvements would help.

Unless your business is selling...

Also, if you're just trying to figure out why your original loop wasn't giving you your list of dates, take a look:

DECLARE @dateDATETIME = GETDATE()

DECLARE @thisYearDATETIME

DECLARE @yearsBackINT = 1

DECLARE @dateTableTABLE

(theDateDATETIME)

SET...

For information about how to set permissions on the reports you created, you can read http://msdn.microsoft.com/en-us/library/aa337491.aspx and other Google searches for "Reporting Services security".

We've all been there. Use process of elimination. The SQL procs you have are extremely simple. Once you verify they're exactly the same on the other server...

If you have .NET 3.5 and SQL 2008 you can use a table valued parameter to pass the whole table of what you want updated all at the same time.

But...

Have you tried suggestions contained in http://www.eggheadcafe.com/software/aspnet/34185324/sql08-fulltextindex-setup.aspx or other top Google page links?

I'm not sure if I really understand what you're saying happens where. A few things to keep in mind, however ...

When your sproc hits the "RETURN", it's done -...

If you don't want to interfere in what output you're getting from the proc, there is a way you can get the return value directly.

In your VB.Net code declare another...

If you don't know whether or not you need Visual Studio then you probably don't. If the time comes that you need it, you'll know it.

Don't pass "" to a parameter of sqlDbType.int ... instead convert it to System.DBNull.Value and you'll be fine.

I don't remember my C# enough to know what happens if you try...