Viewing 15 posts - 35,851 through 35,865 (of 59,099 total)
My apologies. I normally document what I did a lot better but I was in a rush. Here's how I came to those numbers from the excellent description...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 29, 2010 at 5:29 pm
Actually, my bad. I didn't read the whole post to see what the data source actually was. I agree that the Information_Schema views are the ticket in this...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 29, 2010 at 4:46 pm
WayneS (11/29/2010)
CirquedeSQLeil (11/29/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
November 29, 2010 at 4:40 pm
I agree with Scott... the OBJECT_DEFINITION function is documented and easy to use for just about everything except a table. Take a look in Books Online for the details.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 29, 2010 at 4:35 pm
Hi Sergiy,
Glad to "see" you still come around once in a while. 🙂
I understand the basic misgiving there but EXCEPT does only return "distinct" values much like a GROUP BY...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 29, 2010 at 4:26 pm
GSquared (11/29/2010)
Jeff's solution...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 29, 2010 at 4:10 pm
Helical Johan (11/26/2010)
Hi,I need write a regular expression:
1. Must start in caracter - next to any letter.
2. Must end in caracter - next to any number.
For example:
5D-Canada-Alberta-Calgary-5715-#3#3-9990516-V3-Local-8-0-0
My output is:
Canada-Alberta-Calgary
Thanks.....
Will...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 29, 2010 at 6:37 am
roman.goldenberg (11/29/2010)
Thanks...I do this in production for save back up's before altering procedure
As a side bar, backups of this nature are fine but you may want to look into some...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 29, 2010 at 6:35 am
nadersam (11/29/2010)
Thanks Jeff,That's exactly what i will start working on in the next period.
Thanks for the feedback, nadersam.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 29, 2010 at 6:34 am
p.s. If, as your subtitle to the post implies, this is only for log shipping, I recommend you start reading "Books Online" (the free help system that comes with...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 28, 2010 at 10:24 pm
shoukat.shaik (11/28/2010)
how we can perform highavailability solutions
Gosh... people write thousand page books on the subject. I'm sure folks will give you some hints but this is much to large...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 28, 2010 at 10:20 pm
Ashwin M N (11/28/2010)
The cursor I have shown above is just an example the actual is more complicated than above.
Complexity changes nothing here. 99.9999% of the time, there is...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 28, 2010 at 10:17 pm
Sergiy (11/28/2010)
😉
Here how would it look with "classic" SQL:
SELECT DocNo
FROM #Docs QE
WHERE LStatus = 'QE'
...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 28, 2010 at 10:05 pm
sampathsoft (11/22/2010)
Thanks
DECLARE @NextString NVARCHAR(40)
DECLARE @Pos INT
DECLARE @NextPos INT
DECLARE @String NVARCHAR(40)
DECLARE @Delimiter NVARCHAR(40)
DECLARE @AddString NVARCHAR(50)
--SET @String ='SQL,TUTORIALS'
SET @String ='1.2.3 '
SET @Delimiter...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 28, 2010 at 8:21 pm
Adi Cohn-120898 (11/22/2010)
DECLARE @NextString NVARCHAR(40)
DECLARE @pos INT
DECLARE @NextPos INT
DECLARE...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 28, 2010 at 7:48 pm
Viewing 15 posts - 35,851 through 35,865 (of 59,099 total)