Viewing 15 posts - 661 through 675 (of 683 total)
Hi Hugh,
I'm happy for you to use the FOR XML examples, so long as you give me credit ![]()
Good luck with future publishings!
All the...
Ryan Randall
Solutions are easy. Understanding the problem, now, that's the hard part.
October 28, 2005 at 8:00 am
Aw, I hate it when that happens. You spend time on a solution, only to see that someone's beat you to it! ![]()
Oh well,...
Ryan Randall
Solutions are easy. Understanding the problem, now, that's the hard part.
October 28, 2005 at 7:28 am
So it it! I was put off by all those words... ![]()
Ryan Randall
Solutions are easy. Understanding the problem, now, that's the hard part.
October 28, 2005 at 7:09 am
The query below gives the following result, and is safe to run.
Col1 Col2
----------- -----------
123 1
123 2
123 3
124 1
127 1
127 2
CREATE TABLE #TableA...
Ryan Randall
Solutions are easy. Understanding the problem, now, that's the hard part.
October 28, 2005 at 6:25 am
Here's another way to do it if don't know the groups (using Farrell's #Counting table). This code below gives the following result, and is safe to run.
A B C TOTAL ...
Ryan Randall
Solutions are easy. Understanding the problem, now, that's the hard part.
October 28, 2005 at 5:56 am
Good article - thanks Hugh. A shame about the download, but I'm sure you'll get that fixed. ![]()
In case anyone's not familiar with the...
Ryan Randall
Solutions are easy. Understanding the problem, now, that's the hard part.
October 28, 2005 at 4:45 am
I'm probably missing something, but the code below (in blue, between the stars) does the job on my simple dummy data. Run the whole lot below for a demo.
Ryan Randall Solutions are easy. Understanding the problem, now, that's the hard part.
October 14, 2005 at 6:23 am
For anyone who does not yet have SQL Server 2005, here's an article for achieving similar results using a UDF in SQL Server 2000...
http://www.windowsitpro.com/Article/ArticleID/26094/26094.html?Ad=1 (written by Tim Pfeiffer)
Ryan Randall
Solutions are easy. Understanding the problem, now, that's the hard part.
October 5, 2005 at 3:15 am
You can probably do something with a view and an instead of trigger. Something like this (on top of your xml parsing stuff)?...
create view...
Ryan Randall
Solutions are easy. Understanding the problem, now, that's the hard part.
April 1, 2003 at 11:43 am
You can do pretty much anything with 'for xml explicit'. In this case you can do something like this...
create table TempTable (FirstName varchar(50), LastName...
Ryan Randall
Solutions are easy. Understanding the problem, now, that's the hard part.
April 1, 2003 at 11:02 am
Here's how I'd do it (very similar to Greg's, and the same limitations)...
declare @start_date datetime
declare @end_date datetime
set @start_date = '1 jan 2001'
set @end_date = '1 jan...
Ryan Randall
Solutions are easy. Understanding the problem, now, that's the hard part.
February 13, 2003 at 12:22 pm
Funnily enough we started using the categories a week or two ago. We've found that the name of the sql developer works well for us as a category.
Ryan Randall
Solutions are easy. Understanding the problem, now, that's the hard part.
January 30, 2003 at 7:40 am
quote:
If you are talking about making the change on Monday and testing it before it runs live on Fri, I'd argue it...
Ryan Randall
Solutions are easy. Understanding the problem, now, that's the hard part.
January 27, 2003 at 12:03 pm
We primarily use SQL 2000's XML functionality, then apply XSL for HTML reports. For very quick and simple reports where performance is not an issue, we put the SQL...
Ryan Randall
Solutions are easy. Understanding the problem, now, that's the hard part.
January 23, 2003 at 3:55 am
I'm a bit confused by those replies.
David - If the system has to be up and running when it's needed, then is that a non-critical system?
Antares:
a) Scenario 2 isn't necessarily...
Ryan Randall
Solutions are easy. Understanding the problem, now, that's the hard part.
January 21, 2003 at 11:46 am
Viewing 15 posts - 661 through 675 (of 683 total)