this is the meat of sp_spaceused when used against a single table so their are differences in how it is calculating it

/*

** Now calculate the summary data.

* Note...

total size included the log file. What size is your transaction log?

also the restore job will report success even if it did not actually restore any logs because it could not find any with correct LSNs.

It sounds as if your logs...

Grant Fritchey (1/31/2013)

---

Or, look to a third party tool like Red SQL Data Compare & SQL Compare. But you can't use the backup process to only move pieces of a...

if your application is the type that runs as a service and jumps into SQL as soon as it detects it running you could hit problems with the upgrade in...

or use the bcp utility, likely to be the fastest method.

else you are going to need a third party tool

then scripting out the alter login commands the one time is your best bet, and running the script after each restore. If the amount of logins constantly changes, use dynamic...

script upgrade mode is the last step in the upgrade of an instance for 2008 onwards (IIRC). After you install the upgrade, the next time you start SQL it will...

don't take the database offline per se (i.e. don't issue alter database set offline) but do plan an outage and stop all connections to the database before you start, and...

or this is the SQL used by SSMS when running disk usage report and gives you output similar to sp_spaceused (i.e. it includes index space)

SELECT TOP 1000

(row_number() over(order by (a1.reserved...

hows this:

SELECT

OBJECT_NAME(object_id) AS ObjectName

...

OP needs to decide if they want to move particular tables, nonclustered indexes, or just general data to the new drive. 😉

those look like application generated errors rather than SQL ones.

Does the app refer to all objects by schema.name or just name? Sounds like the new version of the application...

sounds like you need to create a new filegroup with its file on the new drive and then move your tables to it by recreating\creating its clustered index.

see -http://www.mssqltips.com/sqlservertip/2442/move-data-between-sql-server-database-filegroups/

if you mean the initial size as shown via the database properties in SSMS this nomenclature is misleading, it is in fact that ACTUAL size of the file, including any...