Search type Search syntax
Tags [tag]
Exact "words here"
Author user:1234
user:me (yours)
Score score:3 (3+)
score:0 (none)
Answers answers:3 (3+)
answers:0 (none)
isaccepted:yes
hasaccepted:no
inquestion:1234
Views views:250
Sections title:apples
body:"apples oranges"
URL url:"*.example.com"
Favorites infavorites:mine
infavorites:1234
Status closed:yes
duplicate:no
migrated:no
wiki:no
Types is:question
is:answer
Exclude -[tag]
-apples
For more details on advanced search visit our help page
Results tagged with Search options user 6318

SQL Server 2005 (major build version 9.00.xxxx). Please also tag sql-server.

1
vote
If you are tracing you will catch all params in your trace. If you want to see the last input from a given connection use DBCC INPUTBUFFER
answered Mar 5 '12 by Eric Higgins
1
vote
Having identified bandwidth as your issue, the only options you have apart from bigger network pipes would be to use some sort of compression or data de-duplication method. SQL Server (08 vers) suppo …
answered Feb 27 '12 by Eric Higgins
0
votes
You are shipping backups of logs, not the actual ldf files. Since the backup mechanism would punt if the restore targets were different, I think you have a risk and would probably need to reinit log s …
answered Mar 29 '12 by Eric Higgins
2
votes
Would an Agent Master Job work for you? Have a look at this: http://msdn.microsoft.com/en-us/library/ms190662.aspx
answered Mar 26 '13 by Eric Higgins
2
votes
As a result of the replication job failure, you could respond with an xp_cmdshell statement to perform a Windows function: http://msdn.microsoft.com/en-us/library/ms175046.aspx xp_cmdshell needs to b …
answered Feb 28 '12 by Eric Higgins
0
votes
The SQL Server Agent is the sender if you are indicating jobs are sending successfully. When running a query manually, you are the sender. You can test by logging into your SSMS query window as the A …
answered Jul 27 '12 by Eric Higgins