Viewing 15 posts - 166 through 180 (of 185 total)
...but when i restart after installing
I hope you mean not just restarting services. Whole physical box should be rebooted because SP3 updates Windows registries, it is important.
September 16, 2009 at 11:47 am
Yes, because you want to provide a seamless failover.
September 16, 2009 at 11:44 am
1. Connect remotely to the first node of cluster through the Terminal Services by physical box name
2. Copy installation package to the local drive
3. Install SP3
4. Reboot a box
5. Verify...
September 16, 2009 at 11:29 am
September 16, 2009 at 8:50 am
Ok, I see your problem.
The login was mapped to the database as the dbo, which is wrong. It happened because this account actually created a database during the installation.
Please...
September 16, 2009 at 8:16 am
Make sure you are running you statement against the right database.
Use this statement:
USE Adventureworks
GO
select object_id('person.document')
September 16, 2009 at 7:14 am
You are running your script against the master database, but you have to run it against your particular database.
Please do it and show the results.
September 16, 2009 at 7:07 am
Do you have a nightly restore of this particular database from another server?
If yes, you have to add this login to there.
September 16, 2009 at 7:01 am
Here is the answer:
The login already has an account under a different user name.
Check users, mapped to the database - one of them mapped from your login.
September 16, 2009 at 6:32 am
Sometimes it is impossible to change database status, because it is corrupted.
Just make sure you don't have space issue and then re-run your job again - the new Restore on...
September 16, 2009 at 6:20 am
Other your weird issues probably related to the discrepancies of SQL Server versions on your servers (different services packs).
September 16, 2009 at 6:03 am
Ok, I've tried scripting out the jobs once more and was unsuccessful.
What do you mean "unsuccessful"?
Just click on "Jobs" node in the Object Explorer of SSMS, then highlight all...
September 16, 2009 at 6:03 am
As I said, just lock the file size and set growing rate to 0.
Look at this info about the best practices:
www.sqlmag.com/Article/ArticleID/39158/sql_server_39158.html
September 15, 2009 at 1:28 pm
Two more things.
There are many reasons for TempDB files grow, it depends on particular case. For instance you may have a procedure, which use temporary tables in a code.
If...
September 15, 2009 at 1:18 pm
The single TempDB data file should be split to the number of files equal the number of CPUs on your server.
All of these files should have exactly the same initial...
September 15, 2009 at 1:09 pm
Viewing 15 posts - 166 through 180 (of 185 total)