Viewing 15 posts - 16,051 through 16,065 (of 59,101 total)
Edvard Korsbæk (12/8/2016)
Original value for starttime is 1800001 (Clarion time figures based upon 1/100 of a sec since 00:00 +1)
Update dbo.timeaccountmovement set
DATO = Getdate() ...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 26, 2016 at 9:08 pm
John Mitchell-245523 (12/8/2016)
EdvardYes. Can you imagine the confusion if it were any other way? You wouldn't know whether you were getting old values or new values!
John
No confusion at...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 26, 2016 at 9:03 pm
Sergiy (12/15/2016)
ScottPletcher (12/15/2016)
Pretty soon you'll see in queries "WHERE Status&8 >0".
I guess I don't see why that's so much worse than a non-bit comparison of "status = 8" or...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 26, 2016 at 8:57 pm
Sioban Krzywicki (12/21/2016)
--Jeff Moden
Change is inevitable... Change for the better is not.
December 26, 2016 at 8:30 pm
SQLUSERMAN (12/25/2016)
Would using UserID column (GUID) or BankAccount column (9 digit integer) as the primary key column be less efficient than using an ID column of type integer...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 26, 2016 at 7:17 pm
With the understanding that some of the human dialog is missing and once you've taken the first step above and you don't mind it not being quite as detailed as...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 26, 2016 at 6:35 pm
halifaxdal (12/26/2016)
It might be possible to enforce some requirement to your client, I bet your boss would ask you not to do so.
Fortunately, I have some good input with my...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 26, 2016 at 5:52 pm
Man that seems like a lot of work. Wouldn't it be easier to just watch the screen during a restore? If it's supposed to be an automated restore,...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 26, 2016 at 3:31 pm
SJanki (12/23/2016)
[moving my question from the wrong forum to here!]
We have all application databases in SQL Server 2008 R2 .
I am looking forward to upgrade the 2008 R2...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 26, 2016 at 3:26 pm
herrypotter090 (12/26/2016)
--Jeff Moden
Change is inevitable... Change for the better is not.
December 26, 2016 at 3:11 pm
Additionally, DELETEs are fully logged no matter which Recovery Model you may be using. Sure, the SIMPLE recovery model removes the information from the Transaction Log File once the...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 26, 2016 at 2:48 pm
halifaxdal (12/26/2016)
Thanks, still very tedious, actually adding one step here because data is eventually to be imported into SQL (or NoSQL), right?
It'll be much less tedious to brow beat the...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 26, 2016 at 2:34 pm
You're already using xp_CmdShell. Search for the following DOS commands to take it to the next level.
REN
FORFILES
ROBOCOPY
Also, learn how to capture the OUTPUT of the xp_CmdShell call in a...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 26, 2016 at 2:24 pm
Heh... I can't help because I don't do these types of things but I think the use of the abbreviation of "CSV" is hilarious. Only Microsoft would name something...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 26, 2016 at 1:27 pm
johnwalker10 (12/25/2016)
Bulk Insert runs inside SQL Server and BCP runs outside
BCP Utility is more flexible than bulk insert -...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 26, 2016 at 1:16 pm
Viewing 15 posts - 16,051 through 16,065 (of 59,101 total)