Rebuild index often needs more free space than your biggest table. Rebuild task makes the database to grow. The space allocated is released, but not shrunk unless you do it...

Is your index optimization custom? Does it run for whole DB?

Do not shrink your database/ log files. It will lead to fragmentation

You can configure SQL server to use more than 2 GB (limit for 32 bit systems), by configuring AWE. So if you are enabling AWE its in the server...

1) Awe is for memory greater than 2GB

2) dbcc sqlperf('Logspace')

That is sql default behaviour. Make the column nullable and create a default constraint.

you should replace datafile_name and logfile_name with there logical file name in single qoutes. Also put the correct backup path.

To find out the file names execute.

Restore filelistonly from...

Please see whether this link helps

http://msdn.microsoft.com/en-us/library/ms190422.aspx

Backup the database

Backup database DB_name to disk='path+filename.bak'

Restore using different name

Reastore database DB_New_name from disk='path+filename.bak'

with move datafile_name='newfilepath', logfile_name='newfilepath'

Neerav,

Your requirement is not clear

If you want to create a file and create all new objects in the new file

1) Add file using alter database command

2) disable auto growth for...

Yes, your query looks very confusing. are trying to write CTE?

like

with P2 as

(SELECT distinct PD.DependentProcessid

FROM ProcessDependencies PD

LEFT JOIN Processes P ON

PD.ProcessId=P.ProcessId

INNER JOIN ProcessGroup PG ON

P.ProcessGroupID=PG.ProcessGroupID

AND PG.OrderID<5

AND PD.Processid=10

AND PD.DependencyType='B')

SELECT P1.ProcessID,

CASE WHEN...

I said its temporary because,

any user logged in to your server will be able to access the remote server. Just a security concern

This may fix the issue for the time being. This will authenticate all user regardless their login. See null in local login

EXEC master.dbo.sp_addlinkedsrvlogin @rmtsrvname = N'linkedserverName', @locallogin = NULL...

check all the variable names you assign.

l@e_date may be treated as a column alias.

Use sp_configure to change the value of 'remote query timeout'

it is in advanced option

You can add data file using alter database

ALTER DATABASE Database_name ADD FILE

(NAME='Logical_name',

FILENAME='Physical_name')

You can move data using

DBCC SHRINKFILE('logical_name','EMPTYFILE')

But I dont know wether it works completely for primary filegroup with system...