Viewing 15 posts - 27,391 through 27,405 (of 59,101 total)
mickyT (2/27/2013)
UPDATE table.Statements
SET field03 = CAST(CAST(field03 as bigint) as varchar(20))
WHERE field03 like '0%'
Otherwise...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2013 at 9:52 pm
Scott Milburn (2/27/2013)
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2013 at 9:34 pm
dwain.c (2/27/2013)
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2013 at 8:47 pm
I dunno... seems to me that if it's iimportant enough to go through all of this to get the printing right, then instaqd of display it on the screen, it...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2013 at 8:17 pm
TheSQLGuru (2/27/2013)
. . .it about as joyous as an aggregated view calling an aggregated view.
You can do THAT TOO in SQL Server?!? Jeez, what a suck-@ss product! :w00t:
BWAAA-HAAAA!!!...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2013 at 8:10 pm
SQL Pizza (2/27/2013)
Got a lot of SOS_SCHEDULER_YIELDS-waits and a very high signal time. Could it also be possible, that we just need more CPUs?
As Gail has already said and the...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2013 at 7:49 pm
GilaMonster (1/30/2013)
http://www.simple-talk.com/sql/performance/finding-the-causes-of-poor-performance-in-sql-server,-part-1/No magic bullets.
And no, adding the pk column to NC indexes is not going to fix lookups, and is probably a waste of time.
I've had some success with adding...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2013 at 7:42 pm
ChrisM@Work (2/27/2013)
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2013 at 7:39 pm
I don't even know how to spell "SSIS". To me, it's a 4 letter word. 😛
Holding you at your word of a consistent format, a bit of the arcane...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2013 at 7:15 pm
Here'a a couple of what sounds like a decent tool I found in 10 minutes using my assistant DBA, Google. 😛
I like this first one the most because I can...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2013 at 5:08 pm
Kingston Dhasian (2/26/2013)
UPDATEOD
SETOD.FirstName = UD.FirstName,
OD.LastName = UD.LastName,
OD.Birthdate = UD.Birthdate,
OD.AreaCode = UD.AreaCode,
OD.PhoneNumber = UD.PhoneNumber
FROM#OriginalData AS OD
INNER JOIN #UpdatedData AS...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2013 at 7:46 am
Jeff Moden (2/27/2013)
TheSQLGuru (2/27/2013)
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2013 at 7:28 am
Benki Chendu (2/27/2013)
However, the server is restaring abruptly and nothing is clear from SQL...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2013 at 7:26 am
It means that the data in the file or the structure of the data isn't what BCP was expecting. I suspect that the only way to find out is...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2013 at 7:21 am
WiRL (2/27/2013)
Awesome that works.Many Thanks
Actually, it doesn't. If you insert more than one rrow into the table that fires the trigger, the trigger will only process one row. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2013 at 7:15 am
Viewing 15 posts - 27,391 through 27,405 (of 59,101 total)