Viewing 15 posts - 18,856 through 18,870 (of 59,072 total)
That might be a decent use but it really depends on how the CLR is written. My suggestion would be to test it for performance in a Dev environment...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 22, 2015 at 6:01 pm
WhiteLotus (12/21/2015)
Sounds good ..I also notice that all databases autogrowth option are 10% . Should I change all of them ?
If the initial size was 1MB, it takes 73 growths...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 22, 2015 at 4:55 pm
koti.raavi (12/21/2015)
Below is the sample query
Select Month1,Month2,Month3......Month24 from #temp
I need to display data like below
Select Month1 as [Dec 2015], Month2 as [Jan 2016],Month3 as [Feb 2016] From...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 22, 2015 at 4:12 pm
I know it's going to sound crazy but it sounds like a network cable, NIC, or Switch/Hub port may have gone bad. It could also be that some genius...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 22, 2015 at 3:49 pm
Eirikur Eiriksson (12/22/2015)
Quick thought, you could possibly remove the spaces in both columns for the comparison, not going to be too efficient though.
... unless you add persisted computed columns...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 22, 2015 at 3:37 pm
You can find out if that's the actual problem. Add OPTION(MAXDOP 1) to the reporting queries to limit to 1 CPU and see what happens.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 22, 2015 at 3:04 pm
Unless there's an actual "connection leak" (extremely rare), there's usually nothing to worry about especially when there's connection pooling. If you do have a "connection leak", you won't have...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 22, 2015 at 2:48 pm
mishka-723908 (12/22/2015)
We have a Warehouse DB server. The main DB is the Warehouse and there are a few auxiliary databases on the server as well. I have a developer who...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 22, 2015 at 2:45 pm
From the article:
This horror story is fictionalized...
Heh... no it's not. It almost perfectly describes what I've been through twice and am still trying to pick up the pieces. 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
December 22, 2015 at 9:35 am
Charlottecb (12/22/2015)
Regards your concern about using the value for any real use, it is only a friendly number used for the contractors so it doesn't matter too much.
If that's true,...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 22, 2015 at 9:10 am
TheSQLGuru (12/22/2015)
--Jeff Moden
Change is inevitable... Change for the better is not.
December 22, 2015 at 9:03 am
ScottPletcher (12/21/2015)
--Jeff Moden
Change is inevitable... Change for the better is not.
December 21, 2015 at 10:34 pm
Something like this is pretty easy if you know about a personal friend of mine... the SQL_Variant datatype. It can be a bit of a fair weather friend so...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 21, 2015 at 10:20 pm
hiram.osiris (12/21/2015)
I have a requirement to apply the latest patches to our SQL Server environments, from SQL Server 2000 to SQL Server 2014. I have a doubt regarding SQL...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 21, 2015 at 8:19 pm
To answer your second question first, someone probably just made a mistake.
To answer your first question, if you have a unique non-clustered and a non-unique non-clustered index on exactly the...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 21, 2015 at 8:15 pm
Viewing 15 posts - 18,856 through 18,870 (of 59,072 total)