shohelr2003 (7/9/2013)

---

Thanks for your...

shohelr2003 (7/8/2013)

---

Dear,

In my database 'myDB', there are three logins as A, B, C. All are "sysadmin". And there is no restriction to access the database objects.

Say, A has done some...

Joie Andrew (7/8/2013)

---

TempDb is used for several things in SQL Server. DBCC CHECKDBs, temp tables, row versioning, etc. If TempDb keeps getting to 2GB in size I would say that...

Have a look at the SQL_CONNECTION memory clerk to see if it's taking up too much memory

Also look at

select * from sys.dm_exec_connections to see how much reads etc have been...

m.rajesh.uk (7/8/2013)

---

there is one ldf file for our database. if we create one more ldf for the same database. then both of these ldfs are shared for transactions or after...

I'm sure this can be done with Resource Governor

If you restore the secondary database from a full backup taken at the primary, provided that all the transaction log backups are in place, SQL Server will do the work.

When...

Firstly, change the "add column" part to just "add".

Secondly, this kind of process will definitely take exclusive locks on the table which will block other processes.

I suggest that you run...

GilaMonster (7/4/2013)

---

SQLSACT (7/4/2013)

---

Hi Gail - Just to confirm, is this part correct?

if you are changing the Clustering key at all with your updates, all nonclustered indexes will be affected as...

GilaMonster (7/3/2013)

---

If you are never modifying any of the columns that are in the index, then the index has no update overhead. It'll still add overhead to inserts and deletes,...

Keep in mind that if you are changing the Clustering key at all with your updates, all nonclustered indexes will be affected as well

restore database [db_name] from disk = 'location\.bak' with replace

As far as I understand, unless the index is filtered, all inserts/updates/deletes will affect all nonclustered indexes.

Think in a row level, not just on a field level

EDIT - I...

Then your production database has high availability. It depends on business requirements. There is no best practice for how close Dev needs to be to Production.

Might be a silly question, are you connected to the database in question when running these commands?