Set the max memory for that instance of SQL Server to a reasonable amount. On a system with 4GB of memory where the server is dedicated to SQL Server...

Unless you have a problem with the network between those servers - it could be much easier to just restore across the network.

RESTORE DATABASE {...}

FROM...

praneethydba (3/6/2014)

---

thanks a lot..

I am going through the link. now today suddenly it went to 25%, I checked the event logs and sql logs. nothing was there to my notice.

I...

Are you on 2008 or 2008 R2? If 2008 R2 you should be using the native compression - which on a 500GB database could get you down to less...

sqlmunkee (2/4/2014)

---

That must be why Dell (who acquired Quest a while back) have added it to their latest LiteSpeed offering, NetVault LiteSpeed for SQL Server. 🙂 Not sure if it's...

Remove the Distinct in the view definition - that is going to eliminate rows from the grouping that are actually included in the procedure.

The distinct will only occur after the...

For user databases - I would use ALTER DATABASE ... MODIFY FILE () to change the file locations, then take the database offline - copy the files to new location...

Task Manager does a really poor job of displaying memory usage - especially for SQL Server. To view memory usage for SQL Server it is better to use perfmon...

If your system consists of multiple databases - and there is never the...

JohnFTamburo (1/7/2014)

---

Is there any identity that is unique? You could cluster on a non-unique ID...

You could also look at using SSIS instead - which would give you the options on the OLEDB Destination to set a commit size and batch size.

Maintenance plans store the history in a different location - to view that history you need to right-click on the maintenance plan and select view history. Viewing the agent...

defyant_2004 (1/6/2014)

---

Let me ask this: If your given a list of computer names that have SQL Server installed and asked to take on managing them, wouldn't you at least...

Markus (1/2/2014)

---

If you have a domain ID that runs the SQL Server service that ID will need to be setup in the new domain... plus that ID will need to...

Probably the most efficient would be to take a backup to a file and put that backup file on the FTP server. The client will then pull it down...