Viewing 15 posts - 48,766 through 48,780 (of 59,102 total)
What's wrong with just...
--===== Create a test variable (not part of the solution)
DECLARE @test-2 VARCHAR(8000)
SELECT @test-2 = '[8/15/2008 10:44:14 AM] [MESSAGE] Batch Archived:[869] nameOfBatch;Archived Path:\\servername\directory\subdirectory'
--===== Return the path
SELECT...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 15, 2008 at 8:46 pm
I think you're missing some data in the other tables. Also, you'll get a much quicker answer if you format the data as outlined in the Link located in...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 15, 2008 at 8:39 pm
Not only should you have a clustered index on a table, even if the column is an unused identity column, but you should have a unique index somewhere on the...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 15, 2008 at 8:31 pm
Thanks for the awesome compliment, Timothy.
It depends on what the client is comfortable with... some won't allow it as a permanent table so I have to code it in where...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 15, 2008 at 7:58 pm
Paul DB (8/15/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
August 15, 2008 at 7:48 pm
Steve Jones - Editor (8/15/2008)
You can click on the author's name and get a list of all his...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 15, 2008 at 7:47 pm
kathyoshea (8/15/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
August 15, 2008 at 7:44 pm
magarity kerns (8/15/2008)
where
a.acct_nbr >...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 15, 2008 at 7:17 pm
Joe Celko (8/15/2008)
Right now, I'd do running totals in a report writer with SQL Server. But my current job uses DB2, so...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 15, 2008 at 7:12 pm
toniupstny (8/15/2008)
Hmmm.... I (re)read the article Jeff pointed to as the follow-up
Heh... it's been out for quite some time...
http://www.sqlservercentral.com/articles/Advanced+Querying/61716/
--Jeff Moden
and frankly did...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 15, 2008 at 7:09 pm
Ed Thompson (8/15/2008)
Good article to grow by, and very much look forward to Part 2.
Thanks Ed... the followup is at the following URL...
http://www.sqlservercentral.com/articles/Advanced+Querying/61716/
--Jeff Moden
Change is inevitable... Change for the better is not.
August 15, 2008 at 7:00 pm
jcrawf02 (8/15/2008)
Steve & company led you in with "T-SQL Crackerjack Jeff Moden..." on today's feature - does that mean there's a prize in every Jeff? :w00t:
Heh... no... just surprizes... 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
August 15, 2008 at 6:52 pm
toniupstny (8/15/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
August 15, 2008 at 6:50 pm
Charles Kincaid (8/15/2008)
Re-read the original article. Jeff points out the problem with using the index and points out that you should use order by instead.
Actually, in the Running Total...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 15, 2008 at 6:46 pm
Thanks for the feedback, David.
--Jeff Moden
Change is inevitable... Change for the better is not.
August 15, 2008 at 6:05 pm
Viewing 15 posts - 48,766 through 48,780 (of 59,102 total)