Viewing 15 posts - 21,391 through 21,405 (of 59,072 total)
This does it and could be fairly easily converted to dynamic SQL if you needed it to be.
SELECT t1.ID, t1.Name, ca.YrMnth, ca.Enrollment
FROM #Table1 t1
CROSS...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 1, 2015 at 9:13 pm
vsamantha35 (2/28/2015)
How to troubleshoot blocking if u r seeing multiple blocking chains? Do I need to kill all the head blockers?
What is the best approach to deal with...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 1, 2015 at 5:11 pm
sql-lover (3/1/2015)
But in my experience , import and export wizard is as fast as bcp. Like I said, I've copied billion records this way and tested with bcp and it...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 1, 2015 at 5:07 pm
Michael L John (3/1/2015)
Of course, assuming you have a LinkedServer already in place.
You do not need to have a linked server to use the import / export wizard.
And, for a...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 1, 2015 at 5:04 pm
Only one way that I know of... restore from backup.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 1, 2015 at 4:48 pm
Tac11 (3/1/2015)
After i divided size (KB) with Rows it came out 30 KB (around) size for each row. So each page contains 8 KB. So a row on my...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 1, 2015 at 4:30 pm
abhijit 71888 (3/1/2015)
This is my first post in this forum...and I need your support badly as I am struggling with this for last couple of days...
Here is the following Data...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 1, 2015 at 4:27 pm
Dunno about how common it is but I don't use SSIS, SSRS, SSAS, Service Broker, or any of the other "add-ons" to SQL Server and I've worked for anything and...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 1, 2015 at 4:26 pm
Solomon Rutzky (3/1/2015)
Interestingly enough, nearly all of them were wrong in the exact same way. They all did their rounding at the presentation layer.
I'm not so sure that's the wrong...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 1, 2015 at 4:01 pm
True enough, Tom, and apologies for being entirely too brief on my previous response. You can limit the BIT "field" (cough, cough, gasp! 🙂 )by adding a NOT NULL...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 1, 2015 at 3:52 pm
sql-lover (3/1/2015)
Grant Fritchey (2/28/2015)
sql-lover (2/27/2015)
djj (2/27/2015)
Grant Fritchey (2/27/2015)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 1, 2015 at 3:35 pm
ANn -425914 (3/1/2015)
When you say most restrictive what does it mean, is it regarding the number of the rows it results?
In our case, using the following join:
Inner Join...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 1, 2015 at 3:15 pm
Heh... spanners are my specialty... especially when they span months. 😛
Thanks again for the help, Eirikur. Your feedback on all of this confirms most of what I thought....
--Jeff Moden
Change is inevitable... Change for the better is not.
March 1, 2015 at 3:08 pm
Yes... I you look at your code...
INSERT INTO audUsers (audType, audDate, audUser, audTxnName)
SELECT 'EditTo' AS Expr1,
'3/1/2015 12:33:06 PM' AS Expr2,
'Sally Brown' AS Expr3,
'LoadUser' AS Expr4,
Users.*...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 1, 2015 at 2:05 pm
Outstanding. Thank you VERY much for the time you've spent on this whether it may have been trivial or not, Eirikur. You obviously took some time to import...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 1, 2015 at 11:00 am
Viewing 15 posts - 21,391 through 21,405 (of 59,072 total)