Viewing 15 posts - 21,181 through 21,195 (of 22,224 total)
Theres a catalog view sys.extended_properties. You should be able to pull it right out of there.
"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
January 26, 2008 at 4:42 am
You could output as XML and then pass it on to the presentation layer, but it'd probably be a lot easier overall to format the output on the app.
"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
January 26, 2008 at 4:38 am
Cool, 128 character three place numbers. I use those all the 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
January 25, 2008 at 1:18 pm
I like Mark's because it will only return those customers who have orders in all the included years. Much more precise.
"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
January 25, 2008 at 9:04 am
It's hardly optimal, but you could:
SELECT...
FROM...
WHERE YEAR(OrderDate) IN (2001,2002,2003,2007)
You could add those values to a temp table & join on it. That would probably be better than than in IN...
"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
January 25, 2008 at 9:02 am
My two cents, use the stored procedure. Cascading deletes is extremely unforgiving. That can be good, but it can be bad. As long as you've got appropriate constraints in place,...
"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
January 25, 2008 at 6:33 am
I did just a bit more searching. I wasn't sure if it was possible to identify the proc you're in, let alone that proc that called you. If you look...
"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
January 25, 2008 at 6:00 am
I've never heard of such a thing. You could simply add a parameter to your function and pass in the calling procs name. It'll be interesting to see if someone...
"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
January 25, 2008 at 5:57 am
You may run into problems with this:
FORMAT(BUMetrics.ProjectCompletionDate, 'mm') AS MONTH, FORMAT(BUMetrics.ProjectCompletionDate, 'yyyy') AS YEAR
That's not TSQL syntax.
"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
January 25, 2008 at 5:53 am
Yeah, I would have expected to see it begin offering completions when you were typing the schema. That's what I see on my machine. Are you using the November CTP?
"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
January 25, 2008 at 5:19 am
I'm a little confused. You don't have any kind of WHERE clause on your queries.
This will be updating all records in the table where the join criteria is true, if...
"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
January 24, 2008 at 11:50 am
You should try enabling the code and getting an estimated execution plan. That will tell you where the problems are.
Most likely you'll see that you're getting a table scan.
"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
January 24, 2008 at 9:23 am
Holy cow. We've been lucky so far then. We've been naming the project after the database. What a mess.
With the initial release, I did find that we were hacking 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
January 24, 2008 at 7:45 am
You could change the default file group first. Probably not a good idea to be mucking with that too regularly, but...
ALTER DATABASE dbname
MODIFY FILEGROUP mygroup DEFAULT
"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
January 24, 2008 at 7:09 am
Make sure you go into Tools, Options and the select the Text Editor and Transact SQL. The general section there has "Statement Completion." You can get it turned on there....
"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
January 24, 2008 at 6:32 am
Viewing 15 posts - 21,181 through 21,195 (of 22,224 total)