Viewing 15 posts - 13,651 through 13,665 (of 22,224 total)
I'm stuck. I thought maybe you were trying to create a temporary global procedure, but I just tried it and those allow for temporary tables as well.
"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 11, 2011 at 8:10 am
My confusion comes from two sources, I don't understand what an sp_procedure is. A stored procedure:
CREATE PROCEDURE MyProcName
(@MyVariable varchar(50))
AS
CREATE TABLE #MyTable (MyId int);
INSERT INTO #MyTable
(MyId)
VALUES
(1),(2),(3);
GO
Absolutely can support temporary tables, so...
"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 11, 2011 at 8:05 am
I guess I wasn't thinking of the data types as "developer" specific information. But yeah, I love spatial data, so there's one.
"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 11, 2011 at 7:43 am
It's because you're trying to run it across databases. The CTE created in the database you're in, not the database you're running against.
I'm unsure of how to resolve that. I'll...
"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 11, 2011 at 7:39 am
Kathi's article on recovery to a point[/url] in time is very good. I have one too[/url]. Basically, assuming you can answer Gail's question with a "yes" this is what you...
"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 11, 2011 at 7:21 am
From the developer point of view? Honestly, not much. Most of the changes were in the BI space and in administration.
"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 11, 2011 at 7:19 am
Koen (da-zero) (1/11/2011)
Grant Fritchey (1/11/2011)
"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 11, 2011 at 7:17 am
Hard to know, but it sounds like there is probably a trigger on the table, your security setting is working with it, your co-workers is not. But, honestly, that's a...
"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 11, 2011 at 7:15 am
It sounds like you have a transaction rollback within one of the procedures, but no begin transaction statement. You have to either add a begin trans statement or remove 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 11, 2011 at 7:13 am
I would suggest you take a look at Michelle Ufford's scripts on index rebuilds and defrags[/url]. She has the most comprehensive and stable approach out 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 11, 2011 at 7:11 am
I don't completely understand what you're trying to do there, but yes, cursors are absolutely going to cause performance to slow down in most circumstances, regardless of whether or 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
January 11, 2011 at 7:09 am
On #3, if you change the data type on existing data, you face the possibility of data loss, which, for most businesses, is a bad thing. So when do 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
January 11, 2011 at 7:05 am
As much as I love people reading my book, I'm not sure that one will help.
What will happen when the CPU is maxed out? Processes start to wait for CPU...
"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 11, 2011 at 7:02 am
SequelSurfer (1/11/2011)
sqlbuddy123 (1/10/2011)
"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 11, 2011 at 5:47 am
Donalith (1/10/2011)
It doesn't use any disk space? Is it faster or slower than a regular, disk-using, restore?
Restore time is about the same as the regular restore because most of that...
"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 11, 2011 at 5:44 am
Viewing 15 posts - 13,651 through 13,665 (of 22,224 total)