Viewing 15 posts - 631 through 645 (of 1,069 total)
This happens when the database was participating in transactional replication but it was removed properly or restored from a replicated database.
To stop this, add the database to replication and...
September 22, 2010 at 11:27 pm
Is TCP/IP enabled under SQL Server Network Configuration for the SQLEXPRESS instance?
Note that after enabling the protocol, the service needs to be restarted.
September 17, 2010 at 3:06 am
Enable TCP/IP protocol using SQL Server Configuration Manager.
September 17, 2010 at 12:35 am
I think, no need to re-install.
Try "... or add features to an existing installation" under Installation in SQL Server Installation Center.
BTW Replication is not a service.
Hope this helps you.
September 16, 2010 at 10:34 pm
Are you thinking that EXEC %% is a different command? It's not. It's the same EXEC.
What is different is %%xxx. These are undocumented and meant for internal use by Microsoft.
September 15, 2010 at 11:09 pm
Nothing happens, I guess. Because policies are stored in MSDB database. Not in other databases.
What are your expectations and concerns?
September 15, 2010 at 10:51 pm
Ali Tailor (9/15/2010)
Thanks for replyI think, to change Job track is some difficult.
Regards
Ali Tailor
MCTS MSSS2k8
Hi Ali,
Positive thinking is very important.
Update your resume and upload it to http://www.naukri.com
Wish you good...
September 15, 2010 at 4:57 am
klineandking (9/12/2010)
i would also like to know how to create a proxy account for the package
In SSMS, expand SQL Server Agent, right click on Proxies and select New Proxy...
Before creating...
September 13, 2010 at 5:15 am
Run dbcc loginfo()
Notice the FileId and Status columns. Status 2 means active.
For example:
FileId ...
September 8, 2010 at 4:52 am
kssirohi (9/8/2010)
There is an option to replicate indexes (clustered/non-clustered) and you dont need to rebuild the index
What/Where is the option (to replicate indexes)?
Please elaborate your reply.
September 8, 2010 at 2:46 am
Check the Replication Monitor for the reason for the latency. You can also check the log-reader and distribution agent job history.
Transaction log size should not be cause of concern.
September 6, 2010 at 6:24 am
Yogirk (9/2/2010)
September 3, 2010 at 5:31 am
Since you have enterprise edition on the production server, my suggestion is to install same (=Developer) edition on staging and development servers too.
September 1, 2010 at 10:55 pm
It looks like system background process was performing Auto-shrink, which did not allow you to have exclusive access to the database to restore.
Disable Auto-shrink and try to restore.
September 1, 2010 at 10:40 pm
Viewing 15 posts - 631 through 645 (of 1,069 total)