Joe (S.),

How can you have no model? Where's the hierarchy represented?

The reason I still think it's better to keep both is efficiency; I worked on a project in which we implemented Nested Sets for a very complex permissions system. ...

Joe,

As Celko says in _Trees and Hierarchies_, you should define the lft and rgt columns OUTSIDE of your main table -- keep the hierarchy in a seperate table. That...

How deep is the hierarchy, and how will it be queried? Are you certain you want to use an adjacency list for this? Have you considered the Nested...

The ROWCOUNT answer, although wrong in this case, was also feasible -- what if there had been 200000 rows in the table and ROWCOUNT was set to 100000?

The transaction was...

Why not store YYYYMM01 -- First of the month -- and then parse the month and year for display purposes on the client?

Does this help:

declare @somevalue varchar(200)

set @somevalue = 'MAPI:{East, Greg}EX:/o=val1/ou=val2/cn=val3/cn=val4'

declare @val3 varchar(20)

set @val3 = 'first replace'

declare @val4 varchar(20)

set @val4 = 'second replace'

SELECT stuff(@somevalue, charindex('/cn', @somevalue) + 4, len(@somevalue), @val3)

+ '/cn='...

Doug,

Probably because I haven't worked with MAPI, you've totally lost me. Can you post exactly what needs to be changed in which strings and by what logic?

I don't understand; are there cases in which that doesn't work? Can you post more sample data and sample output?

Why not just:

UPDATE YourTable

SET YourCol = REPLACE(YourCol, '/cn=Value', '')

I don't recommend that you use EM for that -- What it will do is create a new table minus the columns you've deleted, then copy all of the data...

Is this what you're looking for:

http://www.microsoft.com/sql/evaluation/features/choosing.asp

It depends. Will the output from the view or stored procedure be used in other queries? If yes, then a view is the way to go. If...

Still, though, that DELETE FROM syntax is pretty weird (although not nearly as bad as the UPDATE FROM syntax.. ugh)

Kennith,

Good catch; I thought that the OP had, perhaps, added the SELECT in later to make sure the JOINs were correct...