Viewing 15 posts - 19,516 through 19,530 (of 59,072 total)
andrewbb (9/27/2015)
Jeff Moden (9/27/2015)
There are two problems with you're good solutions, IMHO...1. They're usage is not enforceable.
2. They only address a small part of the problem.
It is a...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 27, 2015 at 5:52 pm
There are two problems with you're good solutions, IMHO...
1. They're usage is not enforceable.
2. They only address a small part of the problem.
--Jeff Moden
Change is inevitable... Change for the better is not.
September 27, 2015 at 11:00 am
From the article:
What I don't get is why we don't just mock up a quick test that we can run in an automated fashion.
First, I loved your observations in the...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 27, 2015 at 10:48 am
myzus2004 (9/25/2015)
The execution plan is Index seek or clustered index scan almost everywhere
Note that "clustered index scan" is a fancy name for "table scan".
--Jeff Moden
Change is inevitable... Change for the better is not.
September 25, 2015 at 5:03 pm
rchantler (9/25/2015)
Is a primary key on a temp table implemented as a clustered index by default, or as a unique index by default?
Both. As on a normal table, if...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 25, 2015 at 4:56 pm
Luis' code is wonderful but it's missing a very important part. Although the use of QUOTENAME certainly helps, you really should delouse the inputs for @CompanyName and @TableName prior...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 25, 2015 at 9:14 am
nikhil.desai1 (9/19/2014)
Hi,As per SQL sever hardening xp_cmdshell is a security risk.
Actually, it's not a security risk if you do it correctly.
First, you should never give an individual proxy privs...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 25, 2015 at 9:01 am
Tac11 (9/24/2015)
Wow. Just asked simple questions, no answer but too much noise!!!!
No problem. Moving on. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
September 24, 2015 at 7:02 pm
Chris-475469 (9/23/2015)
The process is using SSIS but I believe it has been set up quickly just to get it working, not necessarily with performance in...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 23, 2015 at 7:46 pm
Manic Star (9/23/2015)
patricklambin (9/23/2015)
Stewart "Arturius" Campbell (9/22/2015)
Interesting question, thanks SteveAnother of the functions copied from Excel.
I don't think so. These functions have been introduced only to make easier the translation...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 23, 2015 at 7:42 pm
@Phil,
So does that mean that you have to manually click on 480 columns in step 6?
--Jeff Moden
Change is inevitable... Change for the better is not.
September 23, 2015 at 7:29 pm
nancy.gs.chuah (9/23/2015)
I am experiencing the same issue in our PROD environment as well. The performance was relatively fast...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 23, 2015 at 6:33 pm
Christophe.Bejjani (9/23/2015)
That might help
Great links. Thanks and welcome aboard.
--Jeff Moden
Change is inevitable... Change for the better is not.
September 23, 2015 at 6:20 pm
Maxer (9/23/2015)
I had suggested doing the inserts in batches. We were taking data from an OLTP...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 23, 2015 at 6:18 pm
jameslauf (9/23/2015)
I want individual LineitemNumbers per each InvoiceId.
so I cna have Invoice#97865 with LineItemNumbers 1,2,3.
right now I...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 23, 2015 at 5:57 pm
Viewing 15 posts - 19,516 through 19,530 (of 59,072 total)