One data files to multiple data files.

Hello.
I have a database with single data file and i want to split that data across
multiple data files.
Coulf u pls help me how to achieve this
Thanks,
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200601/1please see BOL for Files and Filegroups

one configuration file across multiple packages.

Hi,

At just the point at which I was going to write some verbose schpeel, I found this, which really does it all for me:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1163727&SiteID=1&mode=1

Basically it seems that whilst you can indeed share a config file, it doesn't aggregate sets of say different connection managers, into a superset - you choose to reuse, but it actually overwrites. Any ideas, anyone?

Just edit the Config file to add manually the second configuration. Notice that by doing so you may receive warnings when executing the package as some configurations in the file do not exist in the package using the file. My advice is to use separate configuration files.

|||

'...My advice is to use separate configuration files...'

In the circumstances Rafael, I think this is the best advice. I must say I find it disappointing that one can only share config files in this half-baked way. It would be much better to have one config file shared across 2 packages for say connection managers A,B,C,D,E, where package 1 used connection managers A,B,C, and package 2 used C,D,E.

Maybe that's something for Microsoft to think about...

Thanks for your input Rafael,

Tamim.

|||

BTW,

SQL Server table based configurations behaves more on the way you want. You can have a single table with a row per each configuration value...no warnings if only some are used within the package.

OLTP vs Decision Support

Whilst on the Nth hour (n = many) of my magical journey through MS Sql BOL I've come across OLTP Vs Decision Support. After a couple of searches here could someone shore up the following for me please...

A decision support database is the same as warehouse database.

This is for static data commonly used for reporting and analysis.

OLTP is a live database (accomodates inserts, deletes, updates etc).

Is that right?

Also would it be fair to assume that a decision support database is generally going to be spawned from the historical data of an OLTP database? Any real world examples of these two terms would be greatly appreciated too.

Cheers

DanOLAP

Yes it comes from OLTP...dimensions, fact tables, star schemas, snowflakes...

All the buzz words...

basically you migrate data from your database to basically a read only version of the data...

You then may also have processes to derive data...and store it...for example all the sales for department stores for the month

You derive the data by state, by day, whatever...

However people need to see data that's what you build...

Now query is a lot faster because the work has already been done for the end user...

google up some non platform specific concepts...|||OK, makes sense and I only had to read it twice!

Cheerssql

'OLE DB Destination' failed validation error

Hi,

I'm developing a SSIS package and am coming across this problem:

"Error at myTable [DTS.Pipeline]: component 'OLE DB Destination' (156) failed validation and returned error code 0xC020801C.

Here's the situation with my package. It basically consists of a bunch of tasks to build a database and populate the tables from an Excel file.

The first task runs a SQL file to create all my DB tables, etc. The next set of tasks import data from the Excel file into the tables. All tasks have precedence constraints so that the SQL file will build the DB tables first.

Here's the problem. Everything works perfectly if my database ALREADY exists. The problem comes when the database does not exist. It seems like the SSIS does some sort of schema validation on my dataflow tasks to ensure that everything is ok.

Is there any way to bypass this validation so that my SSIS will run ok without the DB already existing? I know that everything WILL be ok because the ExecuteSQL task will create the structure for me.

I used to work with SQL 2000 DTS, and i never ran into this problem before. Previously, i could run the DTS no problem, however, i just couldn't open the transformations if the DB didn't exist.

Thanks.

Set DelayValidation=True on the Data Flow.