Viewing 15 posts - 601 through 615 (of 1,524 total)
I figured out the problem. I did not have the service account ID that runs on the distribution sql server as a login/user on the publisher. Stupid...
June 3, 2013 at 10:59 am
The odd part of this setup is that both servers are on different domains and use different service IDs to run SQL Server.
I just setup replication between two servers that...
May 31, 2013 at 7:46 am
These are the rights of the service ID:
Act as Part of the Operating System = SeTcbPrivilege
Bypass Traverse Checking = SeChangeNotify
Lock Pages In Memory = SeLockMemory
Log on as a Batch Job...
May 31, 2013 at 7:26 am
Bhaskar.Shetty (5/31/2013)
Try starting SQL Server Agent with administrator priviliage and password, I guess your Sql Server Agent is running on Local System Account.
No it is using the service account already....
May 31, 2013 at 7:13 am
Here our DBA staff is 5, 4 Oracle and 1 SQL Server. We have been trying to find another DBA that has experience in Oracle and SQL Server for...
May 28, 2013 at 10:53 am
If the server name is different you will need to drop and add the new server name.
Even if it is the same server name run select @@servername after you...
May 22, 2013 at 1:48 pm
I'd be quite concerned with a database with no pri keys or indexes and I'd be running profiler to capture all longer running queries and getting some testing done on...
May 22, 2013 at 1:40 pm
This is what I do...
on prod server create this as a job and schedule:
BACKUP DATABASE DB1PROD TO DISK = '\\PQASERVER\H$\backups\DB1PROD_db.BAK'
On test server schedule this as a job...
May 17, 2013 at 6:57 am
Good on the rebuild index/update stats.
Another quick question. When you were running the db on SQL2000 did you run the SQL2008 Upgrade Advisor on the DB? Probably not...
May 16, 2013 at 8:06 am
You need to exclude many things...
.bak
.mdf
.ndf
.ldf
.log
.trc
sqlsrvr.exe
IF Vscan starts to scan your live database files it will bring sql server to its knees.
May 16, 2013 at 7:40 am
Have you at least run update stats at 100% after you moved the db to SQL2008? Microsoft recommends rebuilding all indexes. Your access paths for queries...
May 16, 2013 at 7:38 am
The slow I/O issue is the most difficult thing to track down. It has to do with throughput to your back end storage. Proving it is sometimes...
May 16, 2013 at 5:54 am
SteveEClarke (5/9/2013)
May 9, 2013 at 12:04 pm
SteveEClarke (5/9/2013)
Yes the user account has privileges and also tried the SA account
-
SSMS is 2008 R2 - Sql Server is running SQL 2005 !
Here's a question on that...
May 9, 2013 at 11:56 am
Another thought is are you sure you are using the Management Studio version the same version as the SQL Server the Maint. plan is on?
May 9, 2013 at 7:47 am
Viewing 15 posts - 601 through 615 (of 1,524 total)