Viewing 15 posts - 48,061 through 48,075 (of 59,102 total)
Heh... I can show you a query plan for two queries... one comes up with 100% of the batch size and the other 0%... when you run the queries, the...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 29, 2008 at 2:24 pm
Jackal (9/29/2008)
Jane, thanks for posting your article, one things I did notice was;
"Stored procedures should be named by function and the object they work on. Standard prefix like āpā,...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 29, 2008 at 2:18 pm
Heh... I think we have another set-based convert on our hands. Well done!:D
--Jeff Moden
Change is inevitable... Change for the better is not.
September 28, 2008 at 8:59 pm
Liam Willis (9/22/2008)
This is a very busy database and we took the decision a couple of years ago to switch off the auto update statistics as it was affecting...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 28, 2008 at 8:54 pm
Sounds like you've successfully made a believer out of someone, Matt. š Now, all we have to do is convert the other bazillion folks who think there is any...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 28, 2008 at 8:49 pm
jcrawf02 (9/26/2008)
Normally, that would solve my problem, but I can't create a function. Only temp objects.
Are you creating a stored procedure or just a script? I need to know...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 28, 2008 at 8:28 pm
Except in rare cases like a pass-through view (like a synonym), SELECT * will frequently (usually) make it impossible to do index seeks.
--Jeff Moden
Change is inevitable... Change for the better is not.
September 28, 2008 at 7:24 pm
In other words, start by doing an OUTER JOIN on the homes table with all the other tables. Then, wittle from there.
--Jeff Moden
Change is inevitable... Change for the better is not.
September 28, 2008 at 7:16 pm
You'd get better help quicker if you'd follow the methods in the article in the link in my signature below... š
--Jeff Moden
Change is inevitable... Change for the better is not.
September 28, 2008 at 7:10 pm
cuteprabakar (9/27/2008)
USERS
[userid] [int] NOT NULL,
[password] [int] NOT NULL,
[Fullname] [nvarchar] (50)...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 28, 2008 at 7:08 pm
Not sure if it's possible, but it would also be really cool if we could have discussions on SQL Server about articles not on SQL Server. In other words,...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 28, 2008 at 6:56 pm
Keller (9/28/2008)
Please don't ever eliminate the outtakes. "The human side of Steve Jones" is my favorite part of every editorial! š (Besides the valuable content, of course!)
I'll...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 28, 2008 at 6:54 pm
The OP must like porkchops...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 28, 2008 at 6:51 pm
Not sure what you mean, but if you want to pass an array to SQL, then the following article will help... covers passing of 1, 2, and 3 dimensional arrays...
http://www.sqlservercentral.com/articles/T-SQL/63003/
--Jeff Moden
Change is inevitable... Change for the better is not.
September 28, 2008 at 6:45 pm
Matt Miller (9/27/2008)
Jeff Moden (9/27/2008)
Heh... thanks for posting your solution. Sometimes the problem just boils down to "must look eye." š
Any more references like these and you're going...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 28, 2008 at 6:40 pm
Viewing 15 posts - 48,061 through 48,075 (of 59,102 total)