Are you shrinking the correct file?  It is possible that the file you are attempting to shrink is 'unshrinkable'.  If the particular file is already at 35GB you won't be...

N' = Unicode characters (i.e. 'test' is plain ASCII, N'test' is Unicode)

[dbo]. = the object owner (i.e. [dbo].[myProc] is owned by the dbo alias, [user1].[myProc] is owned {and therefore a...

See the bottom of this article:

http://support.microsoft.com/default.aspx?scid=kb;en-us;328551

HTH,

Art

You should be able to use the INFORMATION_SCHEMA views to determine most if not all of the dependencies.  The views can be seen in the master db and used in...

Try changing the service account login using Enterprise Manager.  If for some reason the service account login was changed outside of SEM several account properties were probably omitted.  SEM alters...

You may want to verify that there are no differences in the Fill Factor and Pad Index properties of the indices.  Fill Factor can be specified at the database level and/or individually...

You might want try xp_regread depending upon your needs.  Checking values in:

If there are no Projects involving multiple Clients for whom you wish to keep separate Documents (e.g. ProjectA, Client1 has Doc1, Client2 has Doc2 and both have Doc3), then there...

I have run into similar errors but generally from client connections...  The fix involved changing the Server Network Utility and Client Network Utility settings.  I completely disable Named Pipes but...

I could but I'm not thrilled about adding an xp to substitute for an existing xp.  I considered that option but have decided to tolerate the error for the time...

Thanx John,

I thought I might have gotten the answer via that link with xp_regenumvalues but ran into the same sort of problem - no temp tables in UDF's so no...

Hi Scott,

I don't think there is a table that will tell you, however, there is an SP, sp_get_composite_job_info, that does.  If you need a table, try using the extended SP, master.dbo.xp_sqlagent_enum_jobs,...

Well, that didn't work...  the suggestions were:  Install SP3a or SP4 and/or remove the bit column from the index (just in case).

There was a bug in pre-SP3 SQL Server that caused issues with bit columns included in indexes (ours was the last column in the index).  If either situation exists, I...

Try searching the web for "Nested Sets".  That method will make managing tree data much easier.  The alternative (and the way you have it now) is "Adjacency List".

There are several examples...