We have reports in SharePoint integrated mode which are really slow when compared to native mode. I have been asked to research and give info on what exactly causes the delays.
Any articles which give me information as to what happens when a report is run from SharePoint server and where does it log.
Recently I read such statments 'When SQL Server is run in "lightweight pooling" mode (fiber mode) and the DTC service is started, unexpected behavior may occur.' Can someone say anything about fibe mode?I am appreciated for it.:)
Durning install I selected Window's Authentication only, but now it seems we may need to use a Mixed Mode with an SA account etc... is there anyway to switch SQL 2005 to use Mixed Mode after the fact?
There is a query which when executed in the grid mode(ctrl+d) takes approx 0.02 seconds(about 21,000 rows) But when I execute in the text mode, it takes about 0.40 seconds!! Why is this difference? Also, when the records from this table are read from a VB application, they are equally slow (as in the text mode!) Why is it so slow on the text mode & relatively faster in the grid mode? Has anyone got any idea on ‘Firehose’ style cursor ?(which may speed up access of data in the VB application)
Currently, our Report Builder is running on Local Intranet mode. I'm investigating what the security implications are in changing it to Internet mode. However, I've not been able to find any documentation on this.
Does anyone know of any documentation that addresses this issue or have experience that they can share with changing Report Builder security zone from Intranet mode to Internet mode?
I have a SQL 2005 OTC. CTP version running on Windows 2003 server.
I would like to find out how the SQL server option changed to Windows Authentication mode from Mixed mode over the weekend. From the SQL log, I don't see when it changed. I would like to see Date/Time and client IP. If I can see User ID (windows) that would be great. Where I can find these info in SQL server?
I was trying to transfer a SQL Server 2000 database to SQL Server 2005 using SQL Server Objects Task. However, The following error message was encountered: "[Transfer SQL Server Objects Task] Error: Execution failed with the following error: "Cannot apply value null to property Login: Value cannot be null..".€œ
I program in C# with SQL Server 2005. I need to connect to Server in security mode.
In connection string I supply UserID = myuser Password = mypassword Persist Security Info = True
In Server I set mixed authentication mode,create login 'mylogin' with password = mypassword after that in my database I create user with username = myuser and loginName = mylogin
There are two problems :
1. in login creation after I fill password, close window and open it again there is old (default) password but not my password 2. Application fails to connect to DB
I have just created some SSIS package. Some package has connection to remote SQL Server 2005 by SQL server authentication mode (not windows).
In the connection property I have setted "save my password", but I have found that after a while the connection is missed and I have to make the Logon. this happen always to random.
Do you know how to keep the connection persistent?
i am facing this problem for quite some time in SQL Server.Ours is an online dedicated server. When addition or deletion of rows is directly performed by right clicking on the row of table, an error occurs "TRANSACTION CANNOT BE STARTED IN FIREHOSE MODE". But, the same row is deleted when a query is written for that through query analyzer.Another same kind of problem, if deletion of rows is directly performed by right clicking on the row of table, error shows as "cannot perform as too many rows are updated" but, the same is done through query analyzer.Can anyone please provide me the solution of this problem and what is the meaning of this "FIREHOSE MODE".Thanks & Regards,Sitangshu Roy
I am facing this problem for quite some time. Ours is an online dedicated server. When the rows of the table are added or deleted by right clicking on the row, an error message is flashed "Cannot start transaction in firehose mode." However, the same row is deleted or new row is added when query is written for that through query analyzer.Another same kind of problem while direct deletion by right click, error message flashes as "Cannot delete the key column as too many rows are updated."May someone please clarify the reasons of these errors and how to rectify them, also what is the meaning of "Firehose Mode"? Thanks & Regards,Sitangshu Roy
Hello FacultiesWhen doing recovery after loss of data files, one would like tostart SQL Server in single user mode. Is this possible?Thanks in advanceDebashish
I installed SQL Server 2005 using Windows Authentication Mode (Windows Authentication)"
How can I change the Authentication Mode of the SQL server from "Windows Authentication Mode (Windows Authentication)" to "Mixed Mode (Windows Authentication and SQL Server Authentication)"?
.NET 2.0 application (Platform target x86) which executes an SSIS package programatically (using Microsoft.SQLServer.ManagedDTS.dll) The issue I am having is that we connect to a Sybase server and even though the .NET app is executing in 32-bit mode, the SSIS pack appears to try load Sybase 64-bit OLEDB drivers.
The error I receive is DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER
When I run on a 32-bit machine all runs fine or if I run using the 32-bit version of DTEXEC the package also runs fine.
Any ideas on how I can force SSIS to use 32-bit drivers when run on 64-bit server programatically?
Our database is in Sql Server 2005 Mode 80 at the moment and we need to switch it to Mode 90. We need a lilst of all incompatibilities that exist.
Essentially, we need a list similar to what the Upgrade Advisor provides for 2000 databases. The only problem is our DB is already in 2005 mode 80. Switching to mode 90 is easy but does not identify all potential problems for us.
Is there a tool that is similar to the Upgrade Advisor that we can run on 2005 Mode 80 databases?
I get an error in my ASP.Net application which states: "The server will drop the connection, because the client driver has sent multiple requests while the session is in single-user mode. This error occurs when a client sends a request to reset the connection while there are batches still running in the session, or when the client sends a request while the session is resetting a connection. Please contact the client driver vendor."
I checked out the database properties, it shows that SQL is set for 'MultiUser' mode. What else do I need to check and how can I fix this?
Hi guys can you help me out---I have developed some SSIS packages in BIDs that use use the Microsoft OLE DB Provider for Oracle for OLE DB - (OLE DB Connection source) and are deploying to a windows2003 x64 server
Q1: How can my package run under 32 bit so it can pick up correct driver msdaora.dll --here "C:Program Files (x86)Common FilesSystemOle DB" folder rather than "C:Program FilesCommon FilesSystemOle DB" folder which is 64 bit and of course has no msdaora.dll in that location
Q2: How can I set up SQL Server Agent to run these packages under 32 bit mode At the moment I use the SQL Server Agent GUI and run as SQL Server Integration Services Package\\File System\\ and package path ie E:ComponentsWarehouse.ETLLoadGroup_Daily.dtsx
I have hit a problem while trying to re-start the server in Single User Mode in order to restore the master database. I run the command sqlservr -m and it locks after the 'non-unicode character set' line each time.
Is there anyone who knows anything about this? Have I missed something or is it a bug? I have researched quite a few books and haven't found any reference to this problem.
This question came to me from a friend and I don't have a lot of details so I apologize in advance. I thought it might be worth a shot to ask here since I couldn't find anything on point in the MS help or KB. A SQL Server 7 database running on an NT 4.0 box is having a full database backup nightly. The backup routine is pretty standard, created using the Maintenance Wizard. It backs up two databases on the server. The problem is that when folks come into work in the AM, the databases are in Single-User mode and someone has to go in and change this. Is this normal behavior? My (admittedly limited) understanding of SQL 7 backups is that they are relatively transparent, and Single User mode is not necessary. You can operate normally other than you can't to any unlogged txn's while the backup is running. They have not done anything explicit to put the databases in Single-user mode when the backup begins. Any ideas how to prevent this from happening? (Or how to automate the switch out of Single-user mode when the backup is completed?)