Viewing 15 posts - 21,646 through 21,660 (of 22,219 total)
ecreese (10/19/2007)
Msg 421, Level 16, State 1, Line 1
The xml data type cannot be selected as DISTINCT because it is not...
"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 19, 2007 at 12:10 pm
I tested using the original query, not the DISTINCT. Hang on.
"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 19, 2007 at 11:40 am
Oops.
Got it. Add this to the inner join:
FOR XML PATH (''), type
so it looks like this:
SELECT DISTINCT LocalID as "@ID"
, (SELECT ItemUrl
FROM foo X
WHERE f.LocalID=x.LocalID
ORDER BY x.photoseq
FOR XML PATH(''),...
"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 19, 2007 at 10:50 am
Just so I had some data to mess with, I modified your query to use something form AdventureWorks:
SELECT A.ProductId "@ID"
,a.Name "Col1"
, (SELECT x.StandardCost
FROM [Production].[ProductCostHistory] X
WHERE A.ProductId=X.[ProductID]
ORDER BY X.StartDate
FOR XML PATH('')
)...
"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 19, 2007 at 8:40 am
Until we get the 2008 MERGE statement, you need to do three passes through the data, joining on the incoming data such that you do a batch of updates where...
"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 19, 2007 at 8:21 am
Luke L (10/19/2007)
Luke L (10/19/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 19, 2007 at 7:08 am
I still don't understand what you mean by tasks & processes. What those are and what you're attempting to compare between the database and the front-end?
Do you mean the queries...
"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 19, 2007 at 6:52 am
I'm one of those flaky individuals who kind of backed into this gig. I did four years in the Navy. I was effectively an inheritor of Robert Fulton, working on...
"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 19, 2007 at 6:31 am
You could try creating a table valued user defined function that uses dynamic sql to run a query against the table you have and then generate a select statement. The...
"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 18, 2007 at 1:03 pm
There are TONS of ways. Here's one simple one:
SELECT * FROM [INFORMATION_SCHEMA].[TABLES]
WHERE TABLE_SCHEMA = 'dbo'
"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 18, 2007 at 12:54 pm
I'm sorry, I don't understand what you're asking.
Do you mean, where are the stored procedures? Depending on the app, there may not be any, but if there are, they're part...
"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 18, 2007 at 12:49 pm
Unless you put a lock on the table as suggested in the previous post, yeah, the second query will try to delete what the first query was doing.
You may want...
"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 18, 2007 at 10:19 am
Derek Karpinski (10/18/2007)
Where you don't need absolute acuracy. For...
"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 18, 2007 at 10:09 am
Sounds reasonable. I guess I'm going to have to get off my dead behind & get my MCDBA.
Seriously though, it doesn't sound unreasonable. You just need to get the infrastructure...
"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 18, 2007 at 9:22 am
Exactly.
Another option might be to keep them in the call app and pass them in as either a delimited list or XML list and then either turn the delimited list...
"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 18, 2007 at 8:36 am
Viewing 15 posts - 21,646 through 21,660 (of 22,219 total)