OK. I got it to work... eh. I'm underwhelmed by this one. I get more out of Red Gate's SQL Prompt, easier.

One serious comment. If documentation is supplied, it really...

Well it sure doesn't work by default. I tried it in 2005 and 2008 and received nothing. I also note, that the answer, ALT-F1, is not listed in the documentation...

Take a look at the execution plan. Usually (and there are exceptions) you'll see that a query with a view and a query without a view, both of which reference...

What he's saying is, you can't refer to tables by variable names in regular TSQL statements. Instead you have to build a dynamic query as a string, inserting your parameter...

Take a look at the OUTPUT clause. You can use that to capture inserted data, including identity values, into a temporary table for use in later processing.

In order to use a foreign key constraint you have to have either a primary key or a unique index/constraint on the table to which you are referencing. Otherwise, you'd...

We ran into a similar situation once, but in an OLTP system. Long story, short, we only had to do this in a few places and the data load was...

Access the INFORMATION_SCHEMA views. There's one for tables, columns, routines, parameters...

You're stuck. You can only reference what constitutes a candidate key, a pk or unique index and then the whole thing or the leading edge... You could create a second...

But you still have to change the context to run the ALTER/CREATE/whatever script on each of the different environments.

That said, listen to Brandie. Fight the very idea of running...

Not seeing the code, this might not be applicable, but if you're creating the same derived tables over and over again as part of the query of the view, you...

Snapshot replication is a one-time, either on demand or scheduled, operation where an entire database structure and all it's data (but not the security settings, etc.) are copied from one...

If I understand the question, the thing you're looking for is a snapshot. That's an immediate copy of the entire database.

Well, that depends. If you have the keys needed to find the right row or rows in the child table and all the columns you want are in the child...

If a PK looks like this:

Col1

,Col2

,Col3

Then in order to reference that as a foreign key, the code would look something like this:

ALTER TABLE [schema].[tablename]

CONSTRAINT [MyFKName] FOREIGN KEY

(Col1

,Col2

,Col3)

REFERENCES [schema].[parenttable]

(Col1

,Col2

,Col3)

The names of...