Use COALESCE.

Just a quick note, you can't have a Primary Key constraint on RecordID in your Address table if you plan to allow for a Customer to have multiple Address rows...

What else could we expect from The...

I think you'll still get that ability with what Lowell's suggesting. Your token transaction history will still be kept in the DownloadOrders table. The view simply queries the...

--Restore the headers so you can get the logical file names

--from the original DB. You'll need these later.

RESTORE FILELISTONLY

FROM DISK='Your backup file/path here'

--Use the logical file names from above...

Huh, there you have it. I was pretty certain that it would go with the first, but I didn't want to rule out #2. I am surprised, though,...

Well, think about a federated server model where you've got identical copies, in terms of schema, of databases on multiple physical servers to spread the processing load out over the...

Mike,

Gail's advice is solid, as usual. I would follow what she's suggested to a T. As far as your SQL Server service account, you should generally run...

Well, just think of the case where you have multiple databases on a server. You may want to limit a login's access to which databases they can access. ...

It kind of depends on the data. In many instances, the data represents 2 different logical sets of data; hence, you have 2 databases. The reason for using...

Again, probably the first one, but the only way to know for sure is to run it and check the plan. The first index seems redundant because it is...

Each user must be tied to their own login. Think of it as 2 seperate levels of security passthrough. A user must have a login set up at...

1. As we've discussed, at a checkpoint, SQL Server writes all dirty pages to the disk. Dirty pages are pages where data modifications have been made but not committed....

Kipp, you're still stuck on this? Based on the mock up that I did,...

They may produce the same results, but they are different. The first query is checking the variable values for an explicit value while the second query is looking at...