Yes, but you need to run that too, not just the print. If you execute the proc in SSMS then you will see the output of the PRINT statement...

You can't just run the print statement as it's referencing a variable. It's the variable @SQLStatement that the error says you must declare. How are you executing this...

You have a PRINT statement after the SET statement:

SET @SQLSTATEMENT = 'BACKUP '+@BTYPE+ @DBNAME+' TO DISK ='''+@BAKPATH+@@SERVERNAME+'_'+@DBNAME+'_'+@TIMESTAM+'_AUTO'+@BTYPEEXT+''''

PRINT 'SQL STATEMENT'

PRINT '-------------'

PRINT @SQLSTATEMENT

If you aren't seeing this statement, then one of...

What is the value of @SQLSTATEMENT before it is executed?

SET @StopTime = DATEADD(MINUTE,-1,CAST(CAST(GETDATE() AS date) AS datetime)+1);

The parameter @BAKPATH will be NULL if unassigned, not a blank space. Change the following line:

if @BAKPATH=''

to

if @BAKPATH IS NULL

The same will need to be done for @ZIPPATH.

Try the following:

--Using a table variable.

DECLARE @data table(col1 XML);

INSERT @data

SELECT

'<data>

<test>

<ID>1</ID>

<Value>100</Value>

</test>

<test>

<ID>2</ID>

<Value>200</Value>

</test>

<test>

<ID>3</ID>

<Value>300</Value>

</test>

</data>';

WITH Result

AS

(SELECT a.col.value('ID[1]','int') AS ID,

a.col.value('Value[1]', 'int')...

If you're considering upgrading to SQL 2012, be aware that the licensing model is changing to per core. Another factor you may want to look at apart from maximum...

Can you post the DDL for the original table and the new table without the partitioning and with a CSV file with the record in question? Are you doing...

From the DDL you posted, the STUDENT_ATTENDANCE table doesn't have a primary key, only the backup table does. Let's assume it does though and I suggest creating the PK...

What happens if you try to create the primary key on the backup table?

What is the result of the following query?

SELECT AbcID, COUNT(*) FROM backuptable

GROUP BY AbcID

HAVING COUNT(*) > 1;

Can...

It depends on the growth projection for the table really. If it is going to stay at 23m rows then a clustered index is fine but if it's a...

Where are you loading the data from? Does the source table not have the same unique index? Are you loading into an empty table? What is the...

Can you post the execution plans?

You can just do a "select * into" to create the backup tables then script the PK and FK and create them on the backup tables. If you need...