Viewing 15 posts - 50,491 through 50,505 (of 59,091 total)
The problem is that you are grouping by the UID which appears to be unique... it won't give you the sum of 150 that way... it will always list the...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 16, 2008 at 11:31 pm
Nope...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 16, 2008 at 11:25 pm
There are a lot of things in SQL Server that have no replacement in ANSI SQL. And, I've never heard of such a converter... basically, portability is a myth.
So...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 16, 2008 at 11:16 pm
jalphor (5/13/2008)
I am working on a project in which someone will drop up to 5 (.txt) files into a directory on a shared drive. I have to go...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 16, 2008 at 11:13 pm
I agree with Mahesh... this type of duplicate data may be a real problem.
However, if that's what you need, just have the final table do a "self update" using 2...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 16, 2008 at 11:04 pm
jim.powers (5/14/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
May 16, 2008 at 10:59 pm
Chris (5/15/2008)
Great forum!!!
Here's my problem. I'm trying to build a course schedule of classes for my job and I want to stop the course descriptions (varchar(max)) from repeating...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 16, 2008 at 10:44 pm
Edward (5/16/2008)
I am just doing a standard duration trace. I am unable to reboot as it is a live system. I will try flushing the procedure cache its mainly...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 16, 2008 at 10:20 pm
If you want that kind of help, then you have to "follow the rules" for posting data. Please click on the URL in my signature line and provide the...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 16, 2008 at 10:15 pm
Which record ID are you going to keep when dupes are present?
--Jeff Moden
Change is inevitable... Change for the better is not.
May 16, 2008 at 9:59 pm
Heh... what yellow dots?
--Jeff Moden
Change is inevitable... Change for the better is not.
May 16, 2008 at 9:37 pm
Ok... I'm going to assume that the Scholar_ID column is the Primary Key and that the start and end dates you want updated are the CheckIn_Date and Vacate_Date columns, respectively....
--Jeff Moden
Change is inevitable... Change for the better is not.
May 16, 2008 at 9:21 pm
I use the same method Michael, posted, as well. Works in 2k and 2k5 equally as well and avoids dipping system tables.
--Jeff Moden
Change is inevitable... Change for the better is not.
May 16, 2008 at 8:41 pm
Heh... Grant will probably agree... I wouldn't teach recursion if they doubled my salary! I've got ethics! 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
May 16, 2008 at 8:39 pm
It would appear that a couple folks didn't test their code... and with disasterous results for the OP...
Here's some code that demonstrates the points that JohnG and Gus were trying...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 16, 2008 at 8:20 pm
Viewing 15 posts - 50,491 through 50,505 (of 59,091 total)