Is drive G: set to be a dependency of SQL Server in Cluster Administrator? If not, you won't see the drive in Enterprise Manager.

If it is a dependency, does the...

I'd be very interested in Chris's solution.

I've always understood that the database cannot be accessed during the actual restore of the transaction log, but can be accessed (if left in...

Is the @FunctionCode variable (or parameter) declared long enough to have the '%' appended to it?

If it isn't, the first method would return the correct rows, but the second method...

You can insert into a table variable using a select statement in the same way you insert into a normal table, e.g.

declare @tab table(objid int,name sysname)

insert @tab select id,name from...

EdVassie,

How do you set the rights detailed in 5) and 6)?

I know about the 'Account is trusted for delegation' setting, but neither I nor our infrastructure team have heard of...

A differential backup will only backup extents that have changed since the last full backup.

Even if just a single byte changes in the extent, the whole extent is backed...

Sp_objectfilegroup doesn't work for indexes (look at sp_helpindex instead).

However, the basic mapping from sysindexes to sysfilegroups (on column groupid) is exactly the same for the base table and the indexes.

...

This information can be found in the sysfilegroups table via sysindexes (for the clustered or heap index - id 1 or 0)

If you look at the system stored proc...

We have a similar problem, and despite help from Microsoft, we are no nearer to solving the problem.

The following link may help:-

http://support.microsoft.com/default.aspx?scid=KB;EN-US;811889

It didn't in our case. We would get the...

You don't need the quotes round the first parameter to datediff. i.e. it should be:-

SELECT scholarship_id

FROM Scholarship.dbo.Scholarship

WHERE Datediff(m,cast..........

I don't have a definitive answer, but we regularly see similar behaviour.

I think it is caused because SQL Server caches the plan for a query dependent on the 'SET' options...

Do the following before restoring:-

alter database dbname set single_user with rollback immediate

Try:- select * from [_SMDBA_].[Incident]

Check the database compatibility level of the target database. If this is set to 70, then the database doesn't support the COLLATE command. If so, change the compatibility level to...

If you don't specify a time, it defaults to 12:00:00.

I suspect your entries for 8/31/2003 will have a time later than 12:00:00.

Change your query to between '8/1/2003 00:00:00' and 8/31/2003...