Viewing 15 posts - 47,251 through 47,265 (of 59,099 total)
I'll take a look, Dooza...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 14, 2008 at 10:10 am
Oh yeah... almost forgot... the reason why the WHERE clause actually works is because of my friend, the NULL value. It's not comparable using most relational operators unless someone...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 14, 2008 at 10:06 am
I thought I'd throw my 2 cents in here... both Seth and Chris did a cool job on this. But, being ever vigilant for every micro-second of performance, I've...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 14, 2008 at 9:53 am
Heh... no problem. I hate typing the code off the top of my head so I keep the script handy at all times.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 14, 2008 at 9:41 am
Garadin (11/14/2008)
Not sure if Jeff is gonna slap me for this one, but we'll see.
Heh... firing porkchop #1... [font="Arial Black"]SLAP![/font] 😛 Ya gotta put a clustered index or, better yet,...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 14, 2008 at 9:04 am
Along with the other suggestions, I'd also take the time to upgrade to at least Service Pack 2. From what I saw on my own machine, SP2 fixed a...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 14, 2008 at 8:42 am
Heh... no, not a waste. In fact, thank you very much! I now know how long it takes to create an index on an INT column that has...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 14, 2008 at 8:38 am
Oh yeah... almost forgot...
The "AT linked_server_name" probably cannot be a variable... you'll need to use dynamic SQL to create the EXEC's, and then execute the dynamic SQL. That can...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 14, 2008 at 8:32 am
Damned smiley faces... wish they could fix that...
Here's the listing without the smiley...
[font="Arial Black"]Execute a pass-through command against a linked server[/font]
{ EXEC | EXECUTE }
...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 14, 2008 at 8:27 am
I've never had to do that before but, according to BOL, here's the correct syntax for how to do it...
[font="Arial Black"]Execute a pass-through command against a linked server[/font]
{ EXEC |...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 14, 2008 at 8:25 am
I also checked the UPDATE() function (you never know)... the one that checks per column... same disappointment...
DROP TABLE dbo.TriggerTest
GO
CREATE TABLE dbo.TriggerTest (ColA INT, ColB INT)
GO
CREATE TRIGGER MyTrigger
...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 14, 2008 at 8:20 am
Wow... I just tried it...
CREATE TABLE dbo.TriggerTest (ColA INT, ColB INT)
GO
CREATE TRIGGER MyTrigger
ON dbo.TriggerTest
AFTER INSERT, UPDATE
AS
SELECT COLUMNS_UPDATED()
GO
INSERT INTO...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 14, 2008 at 7:57 am
When you guys made the "new" TempDB, did you make sure it was still set to the "Simple" recovery mode?
--Jeff Moden
Change is inevitable... Change for the better is not.
November 14, 2008 at 12:13 am
Heh... loops... IF's... RBAR...
The hard part is figuring out how many of each character type is in the password and the following code figure that out nicely. You can...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 14, 2008 at 12:09 am
See the following article for how to do the CSV concatenation along with some pitfalls to avoid...
http://www.sqlservercentral.com/articles/Test+Data/61572/
To help us give you a better/tested answer, take a look at the link...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 13, 2008 at 11:38 pm
Viewing 15 posts - 47,251 through 47,265 (of 59,099 total)