Viewing 15 posts - 21,031 through 21,045 (of 59,072 total)
To add to what Sean posted, you should never do "just" a DELETE because you don't know what to expect. You should always do a SELECT first to see...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 14, 2015 at 10:59 am
skilly2 (4/14/2015)
Jeff Moden (4/13/2015)
http://www.sqlservercentral.com/articles/T-SQL/63681/
As a...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 14, 2015 at 9:29 am
Enumerate each value with ROW_NUMBER() and do a +1 offset self join. Then look for where the "lo" value is greater than the "hi" value (the +1 rownumber). ...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 14, 2015 at 8:58 am
Heh... as a bit of a sidebar, when there's a failure, I "SPAM" folks every 2 minutes to establish a sense of urgency. 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
April 14, 2015 at 8:23 am
Since TRUNCATE is a DDL statement, might it be in the default trace? Haven't used the default trace in a million years so can't recall off the top of...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 14, 2015 at 8:14 am
And to be sure, the query for the view would just be...
SELECT columnlist FROM databaseA.dbo.table UNION ALL
SELECT columnlist FROM databaseB.dbo.table UNION ALL
SELECT columnlist FROM databaseC.dbo.table UNION ALL
etc...
Don't use "*" for...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 14, 2015 at 8:12 am
sdownen05 (4/14/2015)
I guess I was confused about NVARCHAR(MAX). I thought the max was 4000 characters, because when I print the results of my dynamic query it will cut it off....
--Jeff Moden
Change is inevitable... Change for the better is not.
April 14, 2015 at 8:08 am
This is an interesting question. I don't know the answer but I'm happy to "bump" it for you.
Anyone have a clue on this? Seems like it could...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 14, 2015 at 7:33 am
niladri.primalink (4/13/2015)
Hi Jeff,Thanks for your quick reply.
The below link has helped me to solve my problems
Thanks once again.
Thanks for the feedback. That appears to be for Office 2007...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 14, 2015 at 7:05 am
Heh... continuous integration is the only way that you can make the maximum number of mistakes before anyone can even blink because, although humans can really make a mess of...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 13, 2015 at 11:57 pm
Considering that there were more than 30 different hacks trying to get something up and running quickly and then hacking at it more to add more functionality quickly over a...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 13, 2015 at 11:54 pm
Stop using Pivot altogether. Just use a CROSSTAB, which is driven by CASE statements to begin with. See the following article for a primer.
http://www.sqlservercentral.com/articles/T-SQL/63681/
As a bit of a...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 13, 2015 at 11:48 pm
sdownen05 (4/13/2015)
--Jeff Moden
Change is inevitable... Change for the better is not.
April 13, 2015 at 11:42 pm
Wow! Seriously? People actually do that? Why the hell would ANYONE in their right mind trust such a person they've just met with their laptop? That's...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 13, 2015 at 11:38 pm
niladri.primalink (4/13/2015)
I have installed SQL server 2014 and my office is also 2013 64 bit. when i am trying to upload excel file into SQL server I am getting...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 13, 2015 at 11:32 pm
Viewing 15 posts - 21,031 through 21,045 (of 59,072 total)