Blam

148 reputation

bio	website
	location	United States
	age	55
visits	member for	7 months
	seen	Mar 14 at 13:31
stats	profile views	10

Design, develop and maintain C# WPF and ASP.NET business application with (typically large) MSSQL backends. Degree in engineering and got into computing via numerical methods.

	148 reputation	bio	website		visits	member for	7 months
5 badges		location	United States		seen	Mar 14 at 13:31

summary answers questions tags badges favorites bounties reputation activity

30 Actions

suggestions reviews revisions comments badges posts accepts all

Mar 13	comment	How to speed up SQL Server RIGHT JOIN on 100MM+ Records - use TVF? CTE is just syntax. It get evaluated. Is that CTE_T, 500k of ~2MM evaluated multiple times? I think you need post the TSQL
Feb 14	awarded	Scholar
Feb 13	comment	PK Fragmentation on INT IDENTITY column Get what you are saying on maintenance plan. This is a 550 GB database so I need to maintain smart. My problem but you have helped me understand the problem. Thanks again.
Feb 13	accepted	PK Fragmentation on INT IDENTITY column
Feb 13	comment	PK Fragmentation on INT IDENTITY column Query results added to question. I am going to go ahead and mark this as an answer as the question may get closed and I don't know if I can mark an answer on a closed question. Thanks
Feb 13	comment	PK Fragmentation on INT IDENTITY column Agree 10% was messed up. Will changed it to 50% and rebuild after a backup. Kind of a long story but when I was using @@Iden it was causing fragmentation that got fixed by scope_identity - really.
Feb 13	comment	PK Fragmentation on INT IDENTITY column Great tip on fill factor. What about pad index? I will post the table structure.
Feb 13	comment	PK Fragmentation on INT IDENTITY column SSMS - I reorganized and it went to 0.2%
Feb 13	comment	PK Fragmentation on INT IDENTITY column Int32 Inden 1, 1
Feb 13	asked	PK Fragmentation on INT IDENTITY column
Dec 18	awarded	Teacher
Dec 18	answered	How to delete large amount of data from a sql table?
Dec 12	comment	Why is my database stuck in the Restoring state? Why is this tagged .NET?
Dec 8	awarded	Commentator
Dec 7	comment	SQL Server - Ignoring object dependencies to copy a DB (despite some column referenced in a sproc no longer existing) Then fix the question - it clearly states one table and one SP. I get data for one client - what does that have to do with creating the tables and FK? How can deleting a SP that does not have columns cause you to miss errors as the SP was not going to execute anyway? U have corrupt data. Cannot reproduce your data without fixing the corruption. Cannot realistically reproduce the events to re-corrupt the data. Multiple versions of OS and SQL versions. R U going to recreate the same OS and SQL version for the test? An expectation of recreate all errors is just not realistic.
Dec 7	comment	SQL Server - Ignoring object dependencies to copy a DB (despite some column referenced in a sproc no longer existing) Why not just create those two columns on the test server between the create tables and create SPs steps. Or delete creating that SP in the create SP script? Would you really want it to ignore object dependencies even if you could?
Dec 7	comment	SQL Server - Ignoring object dependencies to copy a DB (despite some column referenced in a sproc no longer existing) Still not clear. The specific client you need to export is more than one DB?
Dec 7	comment	SQL Server - Ignoring object dependencies to copy a DB (despite some column referenced in a sproc no longer existing) In the 2nd paragraph you refer to their DB (singular). Not clear to me how multiple severs come into play.
Dec 6	comment	SQL Server - Varbinary Column - Extremely Slow Statistics Update Don't understand how statisticsnorecompute on ID fixed this. The statistic was on Data. AUTO_CREATE_STATISTICS would effect this and is at a database level. And it should not auto create a statistic unless DATA was a predicate of a query. msdn.microsoft.com/en-us/library/bb522682(v=SQL.100).aspx
Oct 31	comment	UDF performance suddenly degraded The other side is can create an index cheap on 200 rows. Some times an index will get the query optimizer to do the right thing. But you are not even doing a join. A reach but maybe try an index on the order by and when you insert sort by that.