Viewing 15 posts - 19,066 through 19,080 (of 59,072 total)
Cody K (11/30/2015)
--Jeff Moden
Change is inevitable... Change for the better is not.
November 30, 2015 at 4:23 pm
rameelster (11/30/2015)
I have partitioned a large table in test database which was performing slow archiving process using the below query
CREATE PARTITION FUNCTION TransactionHistoryPartitions (datetime)
AS RANGE RIGHT FOR VALUES ( '2015-10-05',...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 30, 2015 at 4:14 pm
GilaMonster (11/30/2015)
Those rules should be agreed with your team.
What Gail wrote above is the most important. I'll also [font="Arial Black"]STRONGLY [/font]recommend that the "Team" determine a "standard" and...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 30, 2015 at 4:08 pm
kenny 40254 (11/30/2015)
--Jeff Moden
Change is inevitable... Change for the better is not.
November 30, 2015 at 11:55 am
You are missing the word WITH on the second nolock.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 30, 2015 at 11:51 am
KGJ-Dev (11/29/2015)
Thanks for your reply and basically i am planning to create generic function which will take "table name","column name to makecomma separated" and "where condition" and send...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 29, 2015 at 8:30 pm
I'll also add that being both a Developer and a DBA sounds nice on paper but, as you're finding out, it can be a real bugger. I gave up...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 29, 2015 at 2:28 pm
rameelster (11/22/2015)
--Jeff Moden
Change is inevitable... Change for the better is not.
November 29, 2015 at 1:36 pm
SQLisAwE5OmE (11/28/2015)
I did not test the script yet, but i kind of got an idea...i need to enter the server name, db name and the path details.
In regards to...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 29, 2015 at 1:15 pm
KGJ-Dev (11/29/2015)
below is my sample query
declare @Query nvarchar(max)
DECLARE @Names VARCHAR(8000)
Declare @tablename nvarchar(50) = 'sample',@columnname nvarchar(50) = 'userid',@Condition nvarchar = 'name = test'
SET @Query = ' SELECT ' + @Names...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 29, 2015 at 12:33 pm
siddharthak024 (11/29/2015)
We have to rewrite this query into normal SQL queries without the CTE's.
Gosh... WHY? What's wrong with using a recursive CTE for what it was best designed for?
--Jeff Moden
Change is inevitable... Change for the better is not.
November 29, 2015 at 12:29 pm
dplaut 49149 (11/28/2015)
It is obvious from what I'm seeing that the next step does not have the data in the table just loaded.
What is it that you're seeing to make...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 29, 2015 at 12:13 pm
Speaking of Giving Thanks... thanks to all you folks out there in the armed forces and on the streets as policemen. Sometimes you might ask yourself "What the hell...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 29, 2015 at 10:19 am
When you start talking about tera-bytes for an instance, I'd start thinking about a lot more memory than 64GB per node and I wouldn't think about splitting it up much....
--Jeff Moden
Change is inevitable... Change for the better is not.
November 28, 2015 at 1:10 pm
SQLisAwE5OmE (11/27/2015)
Thanks John for providing the script.
Do you understand how it works and how to control the execution order of the scripts using John's method?
--Jeff Moden
Change is inevitable... Change for the better is not.
November 28, 2015 at 12:42 pm
Viewing 15 posts - 19,066 through 19,080 (of 59,072 total)