9,885 reputation
1737
bio website
location
age
visits member for 4 years, 2 months
seen 2 days ago

Mar
25
answered Recommended number of index for a table
Mar
24
revised High Availability using SQL Server 2012 requires how many licenses
added 42 characters in body
Mar
24
answered High Availability using SQL Server 2012 requires how many licenses
Mar
17
revised Out of the box why is a simple query from a 50gb table taking 5x longer in postgres vs sql server--help?
Syntax fix.
Mar
17
answered Out of the box why is a simple query from a 50gb table taking 5x longer in postgres vs sql server--help?
Mar
16
awarded  Revival
Mar
11
revised Getting all descendants of a parent
Added brief notes on other options
Mar
11
answered Getting all descendants of a parent
Mar
9
comment UPDATE statement not consistent when including NULL fields
In standard SQL any operation with a NULL results in NULL (except if you consider applying specific functions like COALESCE), including comparison, arithmetic, and (as in this case) concatenation. You are not wrong, but your statement holds for much more than SQL Server & string concatenation. Regarding COALESCE: you should probably use that rather than ISNULL for portability too (ISNULL is not part of the standard, COALESCE is) unless you are using subqueries inside the function in which case there can be a significant performance difference.
Feb
26
comment Data Warehousing strategy
@ninjabber: So it is possible, though that technique feels rather "dirty" to me. Deliberately circumventing a process intended for maintaining consistency. All the business logic (stored procedures and triggers in the DB and everything in apps outside that modify data in it) will need to make sure that "don't log this" option is set at the right times and only at the right times - that seems to be an open invitation for some interesting bugs!
Feb
25
answered Data Warehousing strategy
Feb
24
answered Store extended properties and apply to another copy of the database
Feb
16
comment SSIS Import Data and insert data
That sounds like exactly the sort of ETL process SSIS is intended to help with, but you'll need to specify your needs in more detail to get much help beyond "yes, SSIS will do that" - your question is a bit to vague/open to get specific help as it currently stands.
Feb
11
revised check key if exists in other table without fk constraint
Added BL clatification
Feb
11
answered check key if exists in other table without fk constraint
Feb
5
comment Indexing nvarchar(128) in SQL Server
For 3,000 queries against 1,000 rows (unless those queries are very oddly complex, such as many levels of recursive CTE and/or sub-query), indexing is going to make very little difference either way. For larger data and load patterns, see the reference linked by JohnM and use-the-index-luke.com/sql/table-of-contents, amongst others, for useful discussion about index design and use.
Feb
4
revised Does the length of the index name have any performance impact?
added 5 characters in body
Feb
4
comment Should login id and password be stored in separate table
Furthermore: as well as any static salt each account should have an account specific value added to the salt. This makes it impossible to know one password by knowing another and noticing that the hashes are the same. The extra data for the salt could be the user ID, or better still an arbitrary value generated (randomly, or username+timestamp for instance) at the time the hash is made and stored with it (this means if the user reuses the same password after the period that your rules don't permit them to, again this can not be seen from inspecting hashes).
Feb
4
revised Does the length of the index name have any performance impact?
added 748 characters in body
Feb
4
answered Does the length of the index name have any performance impact?