Viewing 15 posts - 256 through 270 (of 314 total)
Very good advise about architects being the first to be cut! So keep your day-to-day skills strong just in case 🙂
I must admit, that over the last 2-3 weeks I...
June 25, 2010 at 4:48 am
Well here is the KB article
http://support.microsoft.com/kb/983332
Just wondering if anyone has more info on this? As we are trying to use VS2010 for the TFS (Source Control) aspect...
June 18, 2010 at 3:45 am
generally that error means that your trace file is still being used/added to. You need to close the trace file then run the INTO table statement.
January 14, 2010 at 4:23 am
What are the details of the linked server connection?
Have you got the correct name for the connection? for SQL connections the name of the linked server is used.
July 18, 2008 at 4:04 am
I have not seen it before, but could it be to do with UAC on VISTA??
It can be disabled in MSCONFIG.
July 15, 2008 at 8:04 am
rbarryyoung (7/14/2008)
graham cleverly (7/14/2008)
July 15, 2008 at 7:53 am
Ok, I have gotten the messaging to work (across servers), but I have one final issue.
The acknowledgement message is not working going from the TARGET to the SOURCE correctly. In...
July 14, 2008 at 5:44 am
If it is non-existant, it starts a new conversation, new GUID, which then gets inserted into the dialog table. Admittedly, there is nothing to catch "bad" conversations. I also clean...
July 14, 2008 at 4:31 am
Both routes specify the port as 4022. So not sure why the one appears as it does.
I have setup Service Broker on another instance of SQL going between 2...
July 11, 2008 at 8:53 am
Using a packet sniffer, it seems that I may have the ports setup incorrectly.
Packet going from source to target:
SrcPort - 4509
DstPort - 4022
Packet going from target to source:
SrcPort -...
July 11, 2008 at 2:59 am
Tried all that and still the same thing!
How does the messaging work?
When the intial message is sent, is it sent to the initiator queue or the target queue?
If...
July 11, 2008 at 2:24 am
Here are my routes:
Source
CREATE ROUTE RouteDataSender
AUTHORIZATION dbo
WITH
SERVICE_NAME = '//Audit/AcMan_DataWriter',
BROKER_INSTANCE = '51E3A8D4-BE8B-4162-8B90-245E321F674A',
ADDRESS = 'TCP://10.0.x.x:x'
GO
Target:
CREATE ROUTE [RouteDataReceiver]
AUTHORIZATION dbo
WITH
SERVICE_NAME = '[tcp://10.0.x.x:x/db_ActivityManagement/Audit/DataSender]',
BROKER_INSTANCE = 'AE6697F2-83BA-48FF-93CF-DC8C7BA40FFA',
ADDRESS = 'TCP://10.0.y.y:y'
GO
Have I done something with these?
July 10, 2008 at 9:48 am
you need to allow xp_cmdshell in SQL 2005.
Its in the Surface Area management. Then it should be
Example
EXEC xp_cmdshell 'dir "c:\"'
July 10, 2008 at 3:03 am
We do employ a very similar method of managing our SQL servers. We have about 30 or so SQ Servers and then most of those are replicated through multiple development,...
February 5, 2008 at 7:32 am
K. Brian Kelley (10/11/2007)
October 11, 2007 at 7:11 am
Viewing 15 posts - 256 through 270 (of 314 total)