Search results for query: *

I'm in the process of converting some DTS packages to SSIS packages and one of the tasks involves manipulating an Excel file (deleting rows, adding columns, rename things, data integrity checks, etc.). I need to programmatically modify the Excel file into a useful format before I can use it...

When you create the package and enable the configurations one of the options in the dropdown is the SQL Table.

We are in the process of moving off our SQL Server 2000 database and on to a SQL Server 2008 database and have ~200 DTS packages that will need to be converted to SSIS Packages. Going through and converting them manually isn't feasible with our constraints. Is there a cheap effective tool to...

It's a table that already exists that I've inherited (I know enough to not have spaces in my column names). Oddly enough, the script previously was able to go into production and this time the only difference was I added a couple of fields to be returned that did not have spaces in their names...

It's not the field itself but the field name that is being changed. I think it has something to do with the transformation process from the file that's being rolled into production into the SQL it is executing.

I have a script of a couple of sprocs that involve some column names that have spaces in them. When I run the script on our test environment (includes the drop and create) it executes without issue. I can run the body of the sproc on production and it executes fine, however the process that we...

The issue is that one subreport may have sales information, one may have inventory information, one may have employee turnover information, and so on. All these are in the same "big" report that is used by upper management.

You could always write the stored proc on the server PB is linked to and point to it that way. I've had stored procs getting data from 3-4 different databases and different DBMS (SQL Server 2005 and Oracle). Once you get the stored proc working properly it's simple to implement in PB.

Is it coming back in your query like that or in the report? If it's in the report there should be a way to change the display settings for the field/column. Otherwise it's probably looking at a local setting on the machine to determine how to handle the negative numbers.

If the ADO connection changes I have to go through and revalidate all the subreports. This is also true if I want to switch between production and test. With the ODBC connection I simply change to where it's pointing and it takes 3 seconds. The validation route takes 30 minutes because of all...

I'm looking for ways to speed up my monstrosity of a Crystal Report. It currently contains about 70 sub reports and 30-35 different stored procedures to get the data (only one stored proc per sub report). There is an awful lot of data coming back for each sub-report (6k-15k records each)...

We'd like to use the ODBC connection instead of the ADO connection as our server is going to be changing soon. I'm confused as what you mean by which database. It's a SQL Server 2000 database. There are about 35 stored procedures that drive all the subreports, and as I mentioned it works fine...

I have a report with probably 70 subreports and each subreport brings back anywhere from 6000-15000 rows (then groups them together so ultimately 7-10 rows display). When I connect directly to the database I have no issues retrieving data however when I use an ODBC connection to retrieve that's...