Hello all,
I have Microsoft iSCSI Initiator (SAN) installed on a SQL Server machine and has this drive acting as a local drive. All the database's data files are residing on this drive, attached with SAN.
It runs as a service "Microsoft iSCSI Initiator" on the SQL Server machine.
Now the question is, when we restart the SQL Server all the databases change their status to "Suspect" and we have to stop all the sqlserver services (all the SQL instances) and start them all up. This is the only temporary solution we came up with.
Could any one has any real solution or had encounter such a problem before?
I set-up my Service Broker comunication on the same SQL Server Instance beetween 2 different DBs.
One DB behave as Initiator and send messages to the SB service setup in the other DB.
I execute the SEND statement from the Initiator and if I count the messages on the sys.transmission_queue before to commit the transaction the count returns 0.
If I try to send a message not compliant with the message type, the count that runs after the SEND returns 1 - far enought.
I'm confused about the first behaviour because from what I understood the Acknolodgment and the removal of the message from the sys.trasmission queue should happen after the COMMIT.
I'm trying to set up a replication of SQL 2005. I have 2 servers running and I like to configure it that the second server takes over the SQL database when the first server fails. The database files are located at a ISCS network drive that can have only 1 initiator. We tried to set up a cluster server, but that seems not possible because of the 32 bit proccesors inside the servers. We have installed windows server 2003 EE on both servers. Is there a way that the second server can take over the connection to the ISCS from the first server??
I am getting the above error when I try to create Notificatioin services new Instance.
Additional Information is
Failed to connect to server ABC(Microsoft.SqlServer.ConnectionInfo)
An error occured while establishing connection to the server.When connecting to SQL Server 2005, this failure may be caused by the fact that under default settings SQL Server deoes not allow remote connections.(Provider : Named Pipes Provider, error 40 -could not open connection to SQL Server)(Microsoft SQL Server error: 53)
Please help me I am new to SQL Server 2005.I can't able to proceed.
I am trying to install Microsoft SQL Server 2005 Reporting Services, Receiving the following error
Microsoft SQL Server 2005 Reporting Services -- Error 1303. The installer has insufficient privileges to access this directory: C:Config.Msi. The installation cannot continue. Log on as administrator or contact your system administrator.
I am already logged in as Administrator and should have all the necessary permissions to install software
When I try to connect to the Reporting Services using Microsoft SQL Server Management Studio, the following error message propmpts up:
_____________________________________________________________ ADDITIONAL INFORMATION: The request failed with HTTP status 401: Unauthorized. (Microsoft.SqlServer.Management.UI.RSClient) _____________________________________________________________
Is there any settings that I need to do in the "Reporting Services Configuration Manager" ?
Hello, I would love to know where people are discussing the book Microsoft SQL Server 2005 Integration Services book by Kirk Hasleden.
I'm on page 41 and I'm getting an error with the example in the "SELECT "2004" FROM Sales.vSalesPersonSalesByFiscalYears" part because there is not a table called Sales.vSalesPersonSalesByFiscalYears in the AdventureWorks database.
Scenario: (1) Initiator/Target are running on different machines; (2) Target is on SQL Standard Edition with service pack 1; (3) Initiator ends the conversation.
If Initiator is running on SQL Express Edition with service pack 1 or 2, €œSend message€? and €œEnd conversion€? will introduce two messages in initiator€™s sys.transmission_queue. One is empty message with correct message type; the other is empty message with no message type. Both of them are from the Target to the Initiator.
If Initiator is running on SQL Standard Edition with service pack 1, with same stored procedure (attached below), there is no message left in initiator€™s sys.transmission_queue.
We like to find the way to make Initiator on SQL Express Edition acting same as it on SQL Standard Edition, namely not left messages in the initiator€™s sys.transmission_queue
CREATE PROCEDURE [dbo].[CreateMessageForQueue] @message varchar(max) AS BEGIN
SET NOCOUNT ON;
DECLARE @handle UNIQUEIDENTIFIER;
BEGIN DIALOG CONVERSATION @handle FROM SERVICE [TCP://Initiator:4321] TO SERVICE N'TCP://Target:4567' ON CONTRACT LogContract WITH ENCRYPTION = OFF;
SEND ON CONVERSATION @handle MESSAGE TYPE LogMessage(@message);
I am not sure if this is a correct forum to discuss on the document posted @ http://www.microsoft.com/downloads/details.aspx?familyid=1c2a7dd2-3ec3-4641-9407-a5a337bea7d3&displaylang=en on SQL Server Integration Services (SSIS) Hands on Training - Creating Custom Components.
I am assuming Microsoft Developers are constantly monitoring this forum.
In the document - SSIS Creating a Custom Transformation Component .doc on Page 2 - Exercise 1 - Writing the no-op data flow transformation component - Task 1 - Create a new C# Class Library Project
The textual description talks about creating a new Visual C# Class Library project in VS 2005 but the screenshot accompanying it shows the creation of new "Integration Service Project" in VS 2005.
Please change the screenshot appropriately to avoid confusions.
Microsoft.AnalysisServices.Viewers.DLL dll in VS 2005 but sometimes it gives an error.
"Code generatio for property 'ConnecitonManager'" failed. Error was:'Property accesor 'ConnectionManager' on object 'AssosiactionViewer1' threw the following exception:'Object referance not set to instance of an object"
Is there anyone here who use "Microsoft SQL Server 2005 Datamining Viewer Controls" in SQLServer2005 FeaturePack ? http://www.microsoft.com/downloads/details.aspx?FamilyID=50b97994-8453-4998-8226-fa42ec403d17&DisplayLang=en
i am using VS2005 Version 8.0.50727.762 (SP.050727-7600) and SQL Server 2005 SP2
Dear All,Access adp on sql-server 2000After upgrating to A2003 updating data with 1 perticular combobox causes theprogram to hangs without any error-msg.Traying to change te combobox recordsource i get this error:This version of Microsoft Access doesn't support design changes to theversion of Microsoft SQL Server your project is connected to. See theMicrosoft Office Update Web site for the latest information and downloads(on the Help menu, click Office on the Web). Your design changes will not besaved.The solution in :http://support.microsoft.com/defaul...kb;en-us;313298tolks about SP 'dt_verstamp007' but I have SP 'dt_verstamp006'What should I do.Is the failure of the combobox also caused by the absence of dt_verstamp007???Filip
I have a query that executes just fine except that it won't recognize varchar(255) ( or any other value within the () ) and if I leave it off like this: varchar, then it executes but it leaves that value as 1 and that is just not very useful for my purposes. This also happens with anything else that requires () to add length such as char(), or nvarchar(), etc... Any ideas?
"Failed to copy objects from Microsoft SQL Server to Microsoft SQL Server "
I keep getting this when trying to copy stored procs from one db to another on the same server. I am using the DTS wizard. I have been able to copy the tables but I need the sp's too, and there are too many to copy one at a time.
In VS 2005, when we choose database connection, we can choose one of the above. My question is in what situations should we choose MS SQL Server Database File (SqlClient), and when should we choose Microsoft SQL Server?
I want to deploy a standalone desktop application with a backend database. Which backend database should I should and which of the above connection should I choose?
There are a few features in the new SQL Server - Reporting Services that I really need in production. I have tested everything and it works great. I am running the CTP version since Microsoft is saying they aren't releasing the release version until 3rd quarter 2008.
Since Microsoft won't sell SQL 2008 until 3rd quarter, can I run the CTP in production until the release and then purchase SQL 2008?
On localhost this application works fine but when I put on remote server. I am getting following errors. For both localhost and server, I am using same remote sql 2000. I will appreciate any help.
Thanks,
Arif
Server Error in '/' Application. --------------------------------------------------------------------------------
ERROR [42000] [Microsoft][ODBC SQL Server Driver][SQL Server]Line 1: Incorrect syntax near ')'. Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: Microsoft.Data.Odbc.OdbcException: ERROR [42000] [Microsoft][ODBC SQL Server Driver][SQL Server]Line 1: Incorrect syntax near ')'.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
End Sub this code worked well. we know sql7 is not compatiable with vista. please tell us how to connect it wiith sql2005 . we downloaded orcas express edition beta. we created a database also. please let u know how to connect with Microsoft SQL Server Compact 3.5 (.NET Framework Data Provider for Microsoft SQL Server Compact 3.5).
I'm not asking a lot. I just want to know if I can connect from anExchange server to a SQl server without having to use Access linkedtables. Surely MS must have had a look at this but I can't findanything out there.Help appreciated.Ginters
The Microsoft Synchronization Services for ADO.NET v1.0 CTP release appeared without fanfare on January 22, 2006. The release contains "v1.0 early CTP" bits for the sync framework and SQL Server 2005 Compact Edition (SSCE) v3.5, the Orcas successor to the SSCE v3.1 RTM bits, which Microsoft released on January 11, 2006. The current code name for Sync Services is OCS (for Occasionally Connected Systems).
Seems to me to resemble a "stealth release."
For more, see http://oakleafblog.blogspot.com/2007/01/microsoft-releases-synchronization.html.
Hi,I am evaluating Microsoft Reporting Services against Business Objectsas a reporting tool against SQL Server. I am primarily a BOBJdeveloper and am finding RS not easy to use. Can anyone provide anyfeedback to the overall comparison between these 2 products as I amfinding RS frustrating and am wondering if it is just a matter ofre-adjusting and spending more time on it or if anyone else is findingRS more trickey to use than BOBJ as wellI would be extremely grateful for any feedback.Many thanks in advanceLA
I have a dataset with rows that I normally would display in a  table control. I have too many columns and I would like each data row to be display on many lines. How is that possible?
