change your select clause to "Select custid, min(custname)" instead of using distinct, and it will work. Will be slower, because of the aggregate, but won't cause an error. ...

Use scope_identity() instead of @@identity

Use scope_identity() instead of @@identity.

Any reason to not store the data in a table and give the appropriate people access to that table (via a simple front-end app)? That would be easier than...

I've actually used a SAN for SQL Server, and at first the admin (outsourced) didn't want me to have any say in how it was set up. He set...

Besides load-testing the proc (set up 1000 connections on your computer and run them all at once, 100 times each), which would reveal any hidden problem in the proc, I...

Judging by the error message, I'd assume the proc you're calling has an unnamed column. Procs can have those. Try running the proc separately and see if one...

I used partitioning in a relatively small database for performance reasons, and it worked quite well.

I had three partitions: Current, Old, Ancient.

Current data was still being worked on,...

rhat (10/15/2007)

---

R L Reid (10/15/2007)

---

Posts: 1, huh? It's obviously a troll, but I'll bite.

rhat (10/15/2007)

---

DBCC commands are wild goose chases when a siimple restore of backup is what's needed...

Since I was job hunting for a DBA position for the first half of this year, I can say a few things from the other side of the equation.

First, job...

The solution I've used was data files (.mdb and clustered indexes) on 1 array, indexes on another array, logs on another array, all were RAID 10.  Worked very well.  That...

I made the mistake, early on in my DBA work, of having an identity primary key and a unique index on the two join columns, for several many-to-many join tables. ...