Viewing 15 posts - 21,691 through 21,705 (of 22,224 total)
No, not a simple equi-join, no. A simple outer join, yep.
http://www.sqlservercentral.com/articles/Advanced+Querying/outerjoinmystery/2382/
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
October 15, 2007 at 8:26 am
Can anyone show me a single instance of any individual walking through 1m records one at a time? Every time I've been given the requirement "we need to see all...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
October 15, 2007 at 7:56 am
Maybe I'm confused, but you can't browse the transaction logs. The error logs, which you can browse, aren't going to show much from "activity" but rather from logged events, errors...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
October 15, 2007 at 7:52 am
antony (10/15/2007)
You can update you query in best way like below
Update TableA set a.col3=b.colc,a.col4=ColD,a.col5=ColE from TableA a, TableB b
Where b.ColA = a.Col1
Its similar like the join Query. Try This...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
October 15, 2007 at 7:35 am
In the interest of completion. Here's the execution plan for the latest solution. I'd stick with the simple join statements:
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
October 15, 2007 at 6:10 am
Actually, I can add one more bit of info:
http://www.simple-talk.com/sql/performance/sql-server-performance-crib-sheet/
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
October 15, 2007 at 5:55 am
Jeff Moden (10/14/2007)
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
October 15, 2007 at 5:46 am
Jeff Moden (10/13/2007)
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
October 15, 2007 at 5:42 am
No, we're not searching against it. We simply return it as XML. I have looked into using the XML indexes, but that nine times data storage that I keep reading...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
October 12, 2007 at 9:32 am
We are using it in some places. The purpose is pretty much self-explanatory, we want to persist XML data and having an XML data type for storage ensures that we're...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
October 12, 2007 at 8:34 am
I can't replicate the behavior. I tried using trusted connections & sql connections and unchecking the "remember password" on the connection window. Once I'm connected to a server, every time...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
October 12, 2007 at 6:19 am
Correct me if I'm wrong, but doesn't the black box trace only keep a rolling set of data? You'll need to set up an actual trace. Make it to file...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
October 12, 2007 at 6:09 am
I have to agree. The inner join seems like the most logical approach.
Using the same temp tables above:
UPDATE #TableA
SET Col3 = b.ColC ,
Col4 = b.ColD,
Col5 = b.ColE
FROM #TableA a
INNER JOIN...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
October 12, 2007 at 5:53 am
I'm not sure I have the precise answer, but I was just reading how certain errors can't be trapped at the moment of execution, but can be at a level...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
October 11, 2007 at 11:58 am
Nothing there, you may want to repost.
However, assuming the XML is well formed, you have multiple options for importing it.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
October 11, 2007 at 11:48 am
Viewing 15 posts - 21,691 through 21,705 (of 22,224 total)