sp_helprotect is probably where you'll want to start.

Not sure if this is it but as I recall I think this is the fastest:

SELECT DATEADD(dd, CONVERT(FLOAT, GETDATE()), 0)

There's an article somewhere on this site called "Windows Utilities for the Database Administrator" or something to that effect which goes into the usage of FORFILES to do something like...

I don't believe you can do IF... BEGIN TRY. I think you need to do something like this:

IF (something)

BEGIN

BEGIN TRY

...

They're no longer system tables, they're now system catalog views technically.

If you're trying to remap users, look into sp_change_users_login.

If all the code to generate the recordset is inside a procedure, change the command type of the data set to "StoredProcedure" and just use the stored procedure name.

By default the installation goes to:

C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\SqlWb.exe

Or you can use sp_help 'tablename'.

Normalization rules would dictate that if every value in that column is a specific and different attribute of the entity then you should keep them there. So long as...

If I'm reading you correctly, I wouldn't use a default. All a default allows you to do is specify a value to be entered for new records if no...

Table variables can be treated a great deal like tables (with some exceptions).

DECLARE@tablevarTABLE (

idcolumnint

,column3nvarchar ( 50 )

)

... later...

SELECTx.column1, x.column2, y.column3

FROMdbo.table1 x

JOIN@tablevar y

ONx.idcolumn = y.idcolumn

I'd only be concerned if you see this same behavior on larger tables/indexes.

As for not being able to rebuild online you need to really understand what's going on. If...

If I'm reading that right there's only 6 data pages in the entire index. What's your rowcount on that table?

I've noticed that the index recommendations kind of fall apart...

In that case you're using a feature which is only available in the enterprise edition of the software. There shouldn't be any difference in the rest of the features.

Try...

Why not use t-sql to do it?

ALTER INDEX some_index ON some_table REBUILD