1,310 reputation
1023
bio website twitter.com/coder4hire
location Manchester, United Kingdom
age 37
visits member for 3 years, 3 months
seen yesterday

Software developer and co-founder of Australian software company Redgum Technologies, been developing since late 80's in a variety of languages, C, C++, VB, .NET, etc... as well as a few niche ones...

Last few years Have been spending the majority of my time in SQL Server databases...


Feb
11
awarded  Nice Question
Jan
17
awarded  Yearling
Jan
10
revised More efficient way to write multiple “AND”?
fixed to handle the `AND` criteria not `OR`, also added on extra info for how to expand to specialist criteria
Jan
10
comment More efficient way to write multiple “AND”?
ignore that request, I see my misunderstanding.
Jan
10
comment More efficient way to write multiple “AND”?
Depending on the query engine and statistics on the table you can get a different query plan when using IN (62,50,70) vs tblBB.GRO_NO = 62 OR tblBB.GRO_NO = 50 OR tblBB.GRO_NO = 70. But the main benefit is concise behaviour. Can you expand on your comment that you don't get the same results as the previous query (please add to your question)? I would hazard that my addition of DISTINCT is where the behaviour is different..
Jan
9
answered More efficient way to write multiple “AND”?
Oct
15
answered What is a Scalable Storage Mechanism for large TTL data collections
Jul
23
awarded  Notable Question
Jul
5
comment Removing superfluous tables with a synchronization?
sounds to me like what you need is to logship with a method in between where you restore the logship (so you can interact with it) and then switch back to the logship...
Jul
5
comment Dealing with identity ranges for transactional replication
@Jez Ah, so you've got NOT FOR REPLICATION set, which means SQL Server is a) allowing replication to insert specified IDs AND b) it is not maintaining a last IDENTITY created (so your next non-replication INSERT is trying to create a row at 2), which is why CHECKIDENT works, you should be able to run just DBCC CHECKIDENT ([TableName]) without RESEED, highnumber as that will just sync up the internal IDENTITY counter with the MAX IDENTITY currently on the table
Jul
5
revised Dealing with identity ranges for transactional replication
added further details on why setting up the table as IDENTITY and 2 possible methods for then handling
Jul
5
comment Dealing with identity ranges for transactional replication
@Jez what type of replication did you setup? (if you set it up as MERGE that will happen, for TRANSACTIONAL it usually doesn't, though replication is highly customisable if you don't use the GUI)
Jul
3
comment Dealing with identity ranges for transactional replication
@Jez you'll need to recreate the table (with IDENTITY) in order to run the DBCC CHECKIDENT... A snapshot of replication will create the table with out the IDENTITY constraint (based on your q I'd say the DBCC CHECKIDENT won't work)
Jul
3
answered Dealing with identity ranges for transactional replication
May
31
awarded  Nice Question
May
24
awarded  Caucus
May
24
awarded  Constituent
Apr
16
awarded  Notable Question
Jan
17
awarded  Yearling
Jan
17
awarded  Popular Question