Viewing 15 posts - 22,951 through 22,965 (of 59,067 total)
To be honest, I use "old fashioned" methods such as building either a written flow-chart or, if it's not that complex a problem, a mental flowchart, and then I "peel...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 9, 2014 at 10:22 am
paul.knibbs (8/8/2014)
Jeff Moden (8/6/2014)
Actually, that's one of the questions that I frequently ask except it's to a million and the results have to be stored in a table.
I actually sat...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 9, 2014 at 9:20 am
As another bit of a sidebar, we could also modify the code to identity the direction of the largest streak or produce 3 rows for each symbol to identify the...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 8, 2014 at 11:13 pm
This will do it. As usual, most of the details are where they belong... in comments in the code. 😉
The following code works with the test harness provided in...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 8, 2014 at 11:03 pm
TheSQLGuru (8/7/2014)
--Jeff Moden
Change is inevitable... Change for the better is not.
August 8, 2014 at 5:30 pm
sgmunson (8/8/2014)
Um... that's not actually an option. Don't get me started on the why...
Heh... been there, done that and totally understood. No explanation needed.
Assemblies are stored in...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 8, 2014 at 3:40 pm
kherald69 (8/8/2014)
You can use a recursive common table expression to achieve this.
That's a recursive CTE that counts. Please see the following article for why that's a bad idea even...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 8, 2014 at 10:18 am
funooni (8/8/2014)
Jeff Moden (8/8/2014)
1. DO A FULL BACKUP!!!!!!!!!!!!
2. MAKE SURE POINT-IN-TIME BACKUPS...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 8, 2014 at 10:15 am
sgmunson (8/8/2014)
--Jeff Moden
Change is inevitable... Change for the better is not.
August 8, 2014 at 10:08 am
I have to get to work but here's a 60,000 ft view of what I would do...
1. DO A FULL BACKUP!!!!!!!!!!!!
2. MAKE SURE POINT-IN-TIME BACKUPS ARE BEING TAKEN111!
3....
--Jeff Moden
Change is inevitable... Change for the better is not.
August 8, 2014 at 9:16 am
sgmunson (8/8/2014)
Gail Shaw? Jeff Moden? Anyone?
To the best of my knowledge, dropping a trigger doesn't drop the underlying DDL but I'm no CLR guru, either. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 8, 2014 at 9:01 am
alex_pixley (8/7/2014)
GilaMonster (8/7/2014)
If partitions 8-13 are empty, this will not save you any disk space.
It's like insulating your home. There is the upfront cost of time and effort. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 7, 2014 at 6:54 pm
MMartin1 (8/7/2014)
http://www.sqlservercentral.com/Forums/FindPost485499.aspx
The way I read it, a clustered index (pk or not) won't necessarily cause a huge slowdown...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 7, 2014 at 6:36 pm
smtzac (8/7/2014)
CREATE TABLE [dbo].[ABCD](
[A] [uniqueidentifier] NULL,
[uniqueidentifier] NULL,
[C] [nvarchar](100) NULL,
[D] [nvarchar](max) NULL,
[E] [nvarchar](max)...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 7, 2014 at 9:09 am
mssqlsrv (8/6/2014)
You can create Server and database audit to check what and who is inserting records in a table.Also if possible use partitions for performance.
Oh, be careful now... partitioning won't...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 7, 2014 at 6:13 am
Viewing 15 posts - 22,951 through 22,965 (of 59,067 total)