Viewing 15 posts - 511 through 525 (of 1,162 total)
Check the settings on your OLE DB destination. Remove any value from Rows Per Batch and make sure Maximum commit size is zero.
Also, it might be worth looking at the...
February 22, 2012 at 8:13 am
Ok, for all intents and purposes, it's the same underlying technology. I'd start by removing the OLE DB destination and just sticking in a row count transformation instead to see...
February 22, 2012 at 6:26 am
Just to check, you've selected "Table or View - Fast Load" for the Data Access Mode of the OLE DB destination?
It's usually blisteringly fast going to SQL Server destinations as...
February 22, 2012 at 5:50 am
If you give the DDL for your tables and indexes, some readily consumable sample data and the actual execution plan of the query, you're likely to get some better advice.
Just...
February 21, 2012 at 8:41 am
If this is for an ETL process to merge data from a load table, you probably want to consider doing all of this within a MERGE statement (dynamic or otherwise),...
February 20, 2012 at 6:40 am
I'm pretty sure you can't accomplish this with INTERSECTS alone - you'd need to break out into dynamic SQL, build your key column list from the table metadata and use...
February 20, 2012 at 5:57 am
For a start, I'd convert your query to use ANSI joins. It probably doesn't make a difference for such a simple query, but I suspect your real world example is...
February 20, 2012 at 5:07 am
Using SSIS is probably the best way to do this. You can do what you're asking in SQL 2k8 with a trace flag I believe (I'll find the link when...
February 17, 2012 at 12:42 pm
Gianluca Sartori (2/16/2012)
If you can't connect to it, you can't connect to named instances (you wouldn't know which port to...
February 16, 2012 at 9:22 am
Yep, that's the whole point of the schema collection. An insert will fail (with a specific XSD validation error) if you try to insert malformed documents
February 14, 2012 at 5:47 am
Sample below:
CREATE XML SCHEMA COLLECTION TestSchema
AS'<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:element name="foobar">
<xsd:complexType>
...
February 14, 2012 at 5:41 am
I think it's pretty much a case of declaring an XML variable using your SCHEMA COLLECTION, then assigning the result of your FOR XML to that variable.
This will then error...
February 14, 2012 at 5:28 am
I'm sure there are people who are doing it, but I see them as being more relevant to OLTP at the moment than OLAP.
In my opinion, in a data warehouse...
February 10, 2012 at 8:43 am
Just my 2p. I was in a similar situation a couple of years ago and thought I'd miss having my head stuck in code/administration 8 hours a day and that...
February 10, 2012 at 7:34 am
Although you can work around it using a UDF that references another table, you can't persist them as they're non-deterministic. If you need to index/persist the result, it might be...
February 10, 2012 at 2:17 am
Viewing 15 posts - 511 through 525 (of 1,162 total)