Viewing 15 posts - 9,166 through 9,180 (of 59,102 total)
Thanks for taking the time to post back, Randy. Since you're one of the folks that needs to support it, do you know how it works?
--Jeff Moden
Change is inevitable... Change for the better is not.
June 14, 2019 at 11:30 pm
Sorry... duplicate post removed.
--Jeff Moden
Change is inevitable... Change for the better is not.
June 14, 2019 at 11:29 pm
Yowch. Thanks for the info, Phil.
--Jeff Moden
Change is inevitable... Change for the better is not.
June 14, 2019 at 11:14 pm
Based on the fact that all execution plans are thrown away during a reboot or restart of the SQL Server Service and you said the server suffered a reboot or...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 14, 2019 at 11:10 pm
You first need to find out what the code that uses the table looks like. DW tables are NOT usually "proper normalized tables". For example, removing the "month" column or...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 14, 2019 at 11:04 pm
The OP is just spamming. It's a BS request to try to get past the SPAM filters. I hate these people and won't do business with any company advertised by...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 14, 2019 at 10:33 pm
Totally agreed and thanks for the the feedback, Jonathan. I also do the "partial backups" to exclude Read_Only file groups, sometimes in concert with having the large table in a...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 14, 2019 at 1:24 pm
hi Jeff, That is going to be useful, at least for me. But I could not get it to work on SQL Server 2008 R2 (not that it is...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 14, 2019 at 1:19 pm
Thanks Sreedhar... Ur expression works but the variable has datetime datatype so it converts it to 6/7/2019 5:00:00 PM format rather than 2019-06-07 17:00:00.000. Anyway Thanks for all ur...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 14, 2019 at 1:13 pm
-- SV: For understanding getdate() and things you need
select SYSDATETIME() as sysdatetime_FYI
, getdate() as getdate_FYI
, cast(getdate() as time) as getdate_TimeOnly
, CONVERT(varchar(15), cast(getdate() as time),100) as getdate_TimeOnly_AMPM
,...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 14, 2019 at 3:33 am
I used to display long strings in a similar matter and even wrote a similar article (didn't know Timothy had already written one back then). A fellow by the name...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 14, 2019 at 2:56 am
I've done this but not the way you want. It's super simple, though. Create another database, move your large table to that, and create a synonym in the original database...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 14, 2019 at 2:50 am
ok thanks for all the posts. First this is a view, and I now know declare statements do not work in a view so I updated the statement to...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 13, 2019 at 5:44 pm
I generally use the SQLinForm plugin for Notepad++, works fine for large code sets and most SQL flavors. 😎
With some settings changes, that actually does a fairly good...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 13, 2019 at 5:40 pm
Why not just create a permanent Tally table? It's probably be useful in other situations. Just wondering...
I actually have both a Tally table and an iTFV that works like...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 13, 2019 at 3:42 pm
Viewing 15 posts - 9,166 through 9,180 (of 59,102 total)