Default Trace

Technical Article

RE: Remove alpha characters

  • Reply

Jonathan, I agree about using 'STUFF' - in fact, when I went back to my code to copy it into my message, I realized that I had used 'STUFF', rather than concatenatation, but re-wrote it to confirm my original claim.

You rated this post out of 5. Change rating

2003-12-08

1 reads

Technical Article

RE: Store Key - Storing Misc Data

  • Reply

By the way, just looked at the thread you posted and I feel that there should NOT be two lookup tables in that situation; statuses of court cases are the same logical types of entity, are they not? "OPEN PENDING TRIAL", "CLOSED CONVICTED", etc (assuming these are actual possible statuses), could all go into a […]

You rated this post out of 5. Change rating

2003-12-05

Technical Article

RE: How to number a group of records incrementally?

  • Reply

drop table #SourceTable go -- building a table to take the place of your source table create table #SourceTable ( idsItem int not null ,idsParent int not null ,intIndex int not null default 0 ) insert into #SourceTable (idsItem, idsParent) select 444, 1 union select 445, 1 union select 446, 2 union select 447, 2 […]

2003-12-03

Technical Article

RE: SELECT FROM a WHERE {end bit of field} not in B..?

  • Reply

Maybe something like: select * from Table2 where substring(email, charindex('@', email) + 1, len(email)) not in (select domain from Table1) Assuming of course that email is not null and will always contain a valid email address. Cheers, mia Life moves pretty fast. If you don't stop and look around once in a while, you could […]

You rated this post out of 5. Change rating

2003-11-27

1 reads

Technical Article

RE: Indexing Bit Patterns

  • Reply

My theory was that since the bitwise AND operator tells you whether or not "this bit pattern is a subset of that bit pattern", an index on the INT field should perform well in this type of query: SELECT Field1, Field2 FROM MyTable WHERE @BitArg = (@BitArg & MyBitField) To test this, I ran a […]

You rated this post out of 5. Change rating

2003-07-01

Technical Article

RE: Replicating stored procedures.

  • Reply

Well then there isn't much to say then. It is not difficult. I would create them in a new publication, because when you change the stored procedure, iw will not replicate the changes. So you will have to drop and re create the publication. Or you can also execute sp_addscriptexec (Check in BOL) by adding […]

You rated this post out of 5. Change rating

2003-06-11

Blogs

SQL Saturday Boston 2024 Slides

By

Thanks to everyone that came to my talks. Slides are below. Best Practices for...

Small Data SF 2024

By

I can’t remember how I heard about Small Data SF 2024, but it caught...

A New Word: Moledro

By

moledro – n. a feeling of resonant connection with an author or artist you’ll...

Read the latest Blogs

Forums

7 sept, scheduled book

By philip.scott

Comments posted to this topic are about the item 7 sept, scheduled book

7 sept, schedlued article

By philip.scott

Comments posted to this topic are about the item 7 sept, schedlued article

6 sept, published book

By philip.scott

Comments posted to this topic are about the item 6 sept, published book

Visit the forum

Question of the Day

Azure Data Lake Storage Gen 2

Azure Data Lake Storage Gen 2 is built on ...?

See possible answers