Viewing 15 posts - 301 through 315 (of 629 total)
To repair using the allow data loss option you execute following
USE [master]
GO
DBCC CHECKDB (Julia, REPAIR_ALLOW_DATA_LOSS)
GO
Before you execute that can you please execute following and attach the results in a text...
March 22, 2009 at 5:59 pm
Instead of checking job history check the maintenance plan history for more details; it might be working for some database but failing for others.
Other issue might be databases that were...
March 22, 2009 at 5:18 pm
1) Yes if first one fails second one will execute. If you begin transaction when there is an error it rolls back so your transaction cannot wrap against both bulk...
March 22, 2009 at 5:14 pm
The other thing you should note is since your secondary server will be at a distance from your main data-center if you make that server active for any database the...
March 22, 2009 at 5:10 pm
SQL Server does not have native load balancing solutions ...
But please have a read at these articles ... they might give you some ideas 🙂
http://technet.microsoft.com/en-ca/library/cc966448.aspx
http://msdn.microsoft.com/en-us/library/aa479364.aspx
Thanks.
Mohit.
March 22, 2009 at 4:52 pm
Activity Monitor is not lying ...
I find that I have queries running other databases because where I opened the query window. In the new SSMS it really hard...
March 22, 2009 at 4:41 pm
After you write the script to delete from each database the schema/users you can use the Microsoft shipped function for each database to do the job...
Read up at http://www.dbazine.com/sql/sql-articles/larsen5/.
Thanks.
March 22, 2009 at 4:35 pm
I can think of two options ...
What you can do is implement a Server side trace; that filters on the text data and only tracks following events:
SP:Starting
SP:Completed
Another option is (might...
March 22, 2009 at 4:23 pm
For Analysis Server have a look at http://support.microsoft.com/default.aspx/kb/910230.
For other question you can change your security settings from SSMS without issues.
Thanks.
Mohit.
March 22, 2009 at 4:18 pm
Error 8964 is corruption in LOB (Large Objects); recommended solution is to run DBCC CHECKDB WITH ALLOW_DATA_LOSS.; you can read more about data corruption errors at http://www.sqlservercentral.com/articles/65804/.
Thanks.
March 22, 2009 at 4:16 pm
Kevin O'Donovan (3/21/2009)
I'm still not clear - is the need for for users logging on to workstations and running a client app to have local admin rights on those workstations...
March 21, 2009 at 7:00 pm
RedGate tools are very smart; if you are just doing compare and update it will only fix data that needs to be changed.
I been using RedGate tools for about year...
March 21, 2009 at 3:53 pm
What windows accounts you use it does not need to be local admin to access resources with in SQL Server.
A windows account can be granted connect permissions then further permissions...
March 21, 2009 at 3:44 pm
Someone must have deleted the file needed to uninstall ...
Look at http://support.microsoft.com/kb/290991 to see how to uninstall manually.
Thanks.
Mohit.
March 20, 2009 at 1:34 pm
What is a staging table?
I use the word "Staging" instead of "temp"; because temp to me implies that after the table is done with it is deleted dropped and no...
March 20, 2009 at 12:08 pm
Viewing 15 posts - 301 through 315 (of 629 total)