That's all well and good, but the question doesn't say "In SQL Server 2005, what...

...and, if you pass the data in as XML (or whatever other method you choose to pass in a chunk of data that you want to work on) then you...

You don't need a trigger...

[font="Courier New"]DECLARE

@UserId UNIQUEIDENTIFIER,

@GroupID UNIQUEIDENTIFIER

SET @user-id = NEWID()

SET @GroupID = NEWID()

INSERT INTO User_Group_Map (UserID, GroupID) VALUES (@UserID, @GroupID)[/font]

Wrap it in a stored proc and you can use...

Here's another vote for "squeal". Been working with a very difficult system lately.

And you know the SCSI interface? It had to have been designed by geeks and not marketing, otherwise...

One thing I find useful is to first see if the vendor of the tool has any suggested standards. It appears that Microsoft offers little guidance in that regard, for...

If all you want to do is execute a stored proc that returns no results then you don't need a DataAdapter/DataSet (you don't necessarily need one even if you do...

Eric Wilson (2/18/2008)

---

With due respect, I'm afraid you missed my point. One (major) goal of the Relational Model was to be as uncluttered as possible. To that end, relations (a.k.a....

Wow, sorry for the multiple posts, not sure how that happened.

Eric Wilson (2/14/2008)

---

Regarding the overall article's topic:

The only possible reason to want an ARRAY type is because of assumptions of how the data will be *physically* organized. But we should...

Eric Wilson (2/14/2008)

---

Regarding the overall article's topic:

The only possible reason to want an ARRAY type is because of assumptions of how the data will be *physically* organized. But we should...

Eric Wilson (2/14/2008)

---

Regarding the overall article's topic:

The only possible reason to want an ARRAY type is because of assumptions of how the data will be *physically* organized. But we should...

In C#, would something like this work? Key is setting the length of the input parameter when you create it. You didn't indicate what type @o is so I assumed...

Have you seen Log Parser? It's a free tool from Microsoft that is very useful for parsing different kinds of log files, including IIS log files. I've used it myself...

A SqlDataAdapter isn't needed if all you want is to get back the output parameter value, but specifying the command type is definitely a good idea. I bit the bullet...

Yeah, that would probably be because ExecuteNonQuery doesn't take any parameters, sorry (you can double-check that by checking on-line help).

So take out the "CommandBehavior.CloseConnection", and then be sure to add...