Viewing 15 posts - 856 through 870 (of 1,155 total)
Just check whether each of your cluster nodes (Assuming that 2 node cluster) are running atleast one sql server instance.
You can do this from Cluster administrator on any node.
Suppose you...
September 15, 2010 at 10:51 am
Ghost Cleanup is an internal SQL Server process that clens up the ghost records.
Whebnver a delete happens the deleted record is not deleted physically. As such deleted records are marked...
September 15, 2010 at 10:36 am
1. Try to move some unnecessary files from the disk if any to another disk.
2. Break the large transaction into multiple smaller transactions.
3. If the transaction is doing bulk...
September 15, 2010 at 10:16 am
Hi Krsavita,
1. You are right.
2. Indexes get fragmented over time due to the the DML activites on them like inserts etc.. This happens due to the page splits.
...
September 15, 2010 at 10:07 am
Steve and Homebrew are correct. Never do Shrink. It causes fragmentation and causes performance problems.
Shrink should be done only when there is an disk space issue.
...
September 15, 2010 at 9:51 am
Then you need to identify the root cause. Find the actual app on the prod box that is using that login to connect to the VM and disable it from...
September 14, 2010 at 11:13 am
It is the problem with the login that is trying to connect to the VM and not with the actual VM. So reinstall doesn't work.
First try to identify what...
September 14, 2010 at 10:43 am
This may occur if there are any filemark errors on the backup device or if the folder has corrupted log backups.
Please check the following link.
http://support.microsoft.com/kb/290787
Try to create a new folder...
September 14, 2010 at 10:25 am
What version of SQL server are you using?
Are you seeing any Key lookups or RID lookups, Table scans or Index scans in the query execution plans?
Execution plan looks fine? ...
September 14, 2010 at 10:12 am
Try to kill the connections accessing the db and then try to bring the db to multiuser mode.
If a particular login is reconnecting to the db even after killing it,...
September 14, 2010 at 10:02 am
George is right. Please check the below link
http://msdn.microsoft.com/en-us/library/ms345408(v=SQL.90).aspx
Thank You,
Best Regards,
SQLBuddy
September 14, 2010 at 9:56 am
Sounds like a plan. Good Luck.
Thank You,
Best Regards,
SQLBuddy
September 13, 2010 at 4:17 pm
Please check if this link helps
http://www.mssqltips.com/tip.asp?tip=1433
Thank You,
Best Regards,
SQLBuDDY
September 13, 2010 at 4:06 pm
Please note that MS recommends not to use more than 10 mirroring dbs per instances. Also there is only one DB Mirroring endpoint per instance.
...
September 13, 2010 at 4:03 pm
You should set the FailoverPartner = MirrorServerName in the conection string for the automatic failover to happen.
Data Source=PrincipalServer;Failover Partner=MirrorServer;Initial Catalog=MyDb;Integrated Security=SSPI
...
September 13, 2010 at 3:52 pm
Viewing 15 posts - 856 through 870 (of 1,155 total)