Viewing 15 posts - 32,431 through 32,445 (of 59,099 total)
I'm NOT a product evangelist for Red Gate... but I definitely like their backup tools. Restores with many log file backups are an absolute breeze which is especially good...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 29, 2011 at 5:40 am
pelusodm (9/26/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
September 29, 2011 at 5:05 am
VGish (9/27/2011)
This works perfectly like what I wanted...But, I didn’t understand this part …Why are we doing this?
ROW_NUMBER() OVER (ORDER BY ID,Date) - ROW_NUMBER() OVER (PARTITION...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 27, 2011 at 7:57 pm
Actually, I made a small mistake. While the code works perfectly for the data given, I left an "opening" for an incorrect sort. Please use the following code,...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 27, 2011 at 7:50 pm
CELKO (9/27/2011)
A table has to be a set, so unless you truly have one and only one part, then you want a plural or collective name.
Heh... that's one more...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 27, 2011 at 6:20 pm
yubo1 (9/27/2011)
You can use sql-code below instead of updatetruncate table table_1
&
INSERT INTO table_1 A (col1, col2, col3, col4, ....)
SELECT B.col1, B.col2, B.col3... FROM table_2 B
The problem is that the OP...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 27, 2011 at 6:15 am
ghanshyam.kundu (9/27/2011)
UPDATE p
SET Part_Cost = I.Vendor_Cost
FROM PART p inner join Part_Supplier PS on p.partid=ps.partid
INNER JOIN Inventory I on...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 27, 2011 at 6:12 am
John,
I agree that there's only one column to be updated here and so it won't make much difference for this example, but using the strictly ANSI syntax for UPDATE in...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 27, 2011 at 6:10 am
VG...
For future posts, please consider the methods for posting "readily consumable" data which are taught at the first link in my signature line below. Since you're relatively new here,...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 27, 2011 at 5:36 am
Give the user absolutely no privs except to call a stored procedure that calls a job with a command task in it.
Better yet... why not just have the user run...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 26, 2011 at 8:24 pm
justintime (9/26/2011)
SELECT
bl_id,
case when rm_type in ('WKSTATION','OFFICE') then 1 else 0 end count_seats
FROM rm
then that works fine, i just need to aggregate my data points. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 26, 2011 at 8:18 pm
jonathan.silver (9/26/2011)
Is the collation setting by user or server based?
and then, if I wanted to make sure all of those funny ascci codes -
¡ ...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 26, 2011 at 8:07 pm
mwendecker7686 (9/26/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
September 26, 2011 at 7:59 pm
bennett_js (9/26/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
September 26, 2011 at 7:05 pm
SQLRNNR (9/21/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
September 26, 2011 at 7:00 pm
Viewing 15 posts - 32,431 through 32,445 (of 59,099 total)