hi!

MS SQL Server does not support the ... CONNECT BY ... START WITH ... recursive select statement syntax as oracle does. pity!

best regards,

chris.

quote:

---

Your query would be faster, smaller, and more easily maintained if you put the values in a table and join to that...

quote:

---

And, when the above answer doesn't work, use CHAR(13) + CHAR(10), which is a CR (carriage return) followed by a LF (line...

try using an *exception handler* on client side ...

best regards,

chris.

simple advice:

don't be bothered by autogenerated numbers, you'll not care for GUIDs you generate as well, would you?

deleting rows when using IDENTITY always will give you "holes" in your sequence,...

sometimes the windows-based "fraction" of DBAs/SysAdmins should look a little bit over the borders and be equally "protective" (good wording!) as their colleagues from other systems.

to my opinion the colored,...

Concerning part I consider:

http://www.sqlservercentral.com/products/xp_msmq/

best regards,

chris.

hi!

just an addition to your discussion: aggreeing with frank, i'd not suggest using VARCHAR columns that big at all. you should simply use datatype "TEXT" (physically it is stored differently).

if...

hi!

for convenience, consider the following function (LPAD):

CREATE FUNCTION fn_lpad (

@p_value VARCHAR(50),

@p_char CHAR(1),

@p_digits INT) RETURNS VARCHAR(50) AS

BEGIN

RETURN REPLICATE(@p_char, @p_digits...

hi!

depends on how complex your replication environment is. the more complex, the more "yes" i'd suggest.

best regards,

chris.

hi!

you should *avoid* something like a procedure/function which sort of selects a count and increments by one. why? think of it:

* everytime you insert a record, you'll have to query...

hi!

have a look at

http://www.sqlservercentral.com/scripts/contributions/246.asp

for more comprehensive information

best regards,

chris.

if you want to get information about all your indexes (regardless if they are primary keys, unique keys or simple indexes) take a look at:

http://www.sqlservercentral.com/scripts/contributions/246.asp

best regards,

christian.

hi!

check CASE in BOL! BOL = "Books OnLine" of SQL Server, a very valid source of very *basic* and advanced information!

regards,

chris.

hi guys!

keep it simple: anyone checked if sql*net/net8 including odbc driver was properly installed on your sql servers?

0x80004005 is a generic COM error indicating E_FAIL (operation failed, not catastrophic) and...