Viewing 15 posts - 50,656 through 50,670 (of 59,099 total)
Actually, "It Depends". You can trick it... see the following...
http://www.sqlservercentral.com/articles/Advanced+Querying/61716/
--Jeff Moden
Change is inevitable... Change for the better is not.
May 11, 2008 at 8:54 am
The problem is that the stored procedures you're calling have been written to only handle 1 section at a time. Usually, the only way to use such a thing...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 11, 2008 at 8:41 am
Actually, the real reason why I write is because... I can't remember stuff no mo'. 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
May 10, 2008 at 5:05 pm
Carl Federl (5/10/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
May 10, 2008 at 5:02 pm
creeds (5/9/2008)
Thanks for the feedback and the code you posted. What version of SQL Server are you using? I might be able to turn a treat for you...[/quote]
Jeff,
We're...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 10, 2008 at 4:59 pm
ALZDBA (5/10/2008)
Jeff Moden (5/9/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
May 10, 2008 at 4:57 pm
Thanks, Michael.
--Jeff Moden
Change is inevitable... Change for the better is not.
May 10, 2008 at 7:57 am
This is the same thing that I just went through... I thought for sure that my latest article was on something very obvious. It turns out that it's not...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 10, 2008 at 7:32 am
Michael,
You have a line of code that looks like the following...
else if @s2>=@s1 and @s2 @f1
What is the missing operator after AND @s2?
--Jeff Moden
Change is inevitable... Change for the better is not.
May 9, 2008 at 6:41 pm
RyanRandall (5/9/2008)
Looks like another use for the 'tally' table...
Spot on... 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
May 9, 2008 at 6:19 pm
jprakasam (5/9/2008)
Himy location table has N number of records.
Do you mean N number of Locations?
--Jeff Moden
Change is inevitable... Change for the better is not.
May 9, 2008 at 6:06 pm
I agree with Sergiy... however, sometimes you gotta do what ya gotta do.
Post your code so we can try things out...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 9, 2008 at 5:48 pm
Would "context switching" work for you? Here's the example from Books Online...
-- Switch execution context to the dan1 user account.
EXECUTE AS USER = 'dan1';
-- Execute the DBCC statement.
DBCC CHECKDB...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 9, 2008 at 5:46 pm
HENRY DAVIS (5/9/2008)
select * from SYSOBJECTS where name = 'table_name'
--(1 row(s) affected)
select * from dbo.table_name
--Server:...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 9, 2008 at 5:19 pm
Just a recommendation... Like you said, use ISNULL... don't mess with the default server settings on this...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 9, 2008 at 5:02 pm
Viewing 15 posts - 50,656 through 50,670 (of 59,099 total)