I'm working on a DB that will be used in separate physical locations. These DBs will be identical in structure and completely independent of each other. Whilst some tables will retain similar or identical information, there is a large amount of content that will diverge.However, there is a central location that will need to manage these DBs. There will be a requirement from this central location to run reports, often comparing data between them, and to push data into each child location. There is no requirement for the child locations to 'share' information and indeed the volume concerned and the intermittent/low-bandwidth nature of their connections would make this undesirable. If an individual selection of data does need to be shared between I'm happy for it to be uploaded centrally, a decision made, and manually pushed to each child-location.
Which brings me to my real question. Should I try and include composite Primary Keys in many of the tables (to include probably an incrementing number and another field of site ID) so that when I absorb them all back centrally I can put them into one large DB. Or should I keep them as separate DBs in the central location and use some fairly 'normal' mechanisms for mirroring to sites; accepting that this will make running comparisons between them more difficult and potentially more difficult to write interactivity for centrally?
The best 'real world' comparison I can think of is transactions in retail shops. How do these transaction logs get stored centrally when they're all generating individual transaction numbers that are only unique in that location?
I'm having an issue with what appears to be SQL Server 2005 deciding to randomly ignore new connections.
I currently have two virtual servers - one running just SQL Server 2005, the other running Reporting Services, Windows Sharepoint Services and Team Foundation Server.
For 3 weeks, it was all working perfectly, then on Wednesday night the server (and both Virtual Servers) was rebooted after installing the latest updates for Windows. Since then, I've had this issue.
It will work fine for a while, then it'll start throwing loads of Errors and Warnings into the Event Log, all along the lines of unable to connect to the database. The Reporting Services Configuration utility throws up the same problem. Then randomly, it'll start working again.
If anyone has any ideas, they would be much appreciated as this is driving me crazy!
I am experiencing intermittent connection problems with the Northwind database and sql server express. The most frequent error message indicates that I am already logged in and will not allow another user.
The odd thing is that even when I am locked out I can access a Northwind database from another connection on Server Explorer.
I ran code to demonstrate simple binding for two text boxes, no problem. I added a project to show complex binding using the datagrid view tool, but could not get past selecting the database.
I tried the same simple binding project on another computer running a beta version of VS 2005 Pro and could not connect to Northwind on that computer also. (Two different Northwind databases, different computers)
A couple days ago I restored the database in Solutions Manager and that helped for a while, but I should not have to resort to that, I know.
How do I remove the user lock? I tried Solutions Manager Express with the first computer but could not access the database in the management module.
I'm getting an intermittent error 'DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER' when attempting to connect to an Access mdb. We have a weekly package that fails almost every other week. The package uses a FileSystem task to copy an Access mdb which we use as a template. It has a single table structure which is empty. The FileSystem copy task creates the 'clone' in a different folder with a new file name. The new file name has the current date embedded in it. The next task is a DataFlow task which fills the single Access table with data. It uses an OLE_DB connection to the Access mdb. Since the destination mdb is created at runtime in the FileSystem task, I have set the DelayValidation = True for the DataFlow task. The package is called from a 'master' package via an Execute Package Task. The master package is launched from a web application. Interestingly, when I use the 'restart from checkpoint' feature it restarts the package at the DataFlow task and runs it successfully. I have used the 'restart from checkpoint' after each failure and it has always worked. When I try to isolate the problem in a test package I am unable to reproduce the error. Our SqlServer version is Enterprise Edition (64-bit) with SP2.
Anyone have a similar experience? Thanks in advance.
We have a SQL 2005 clustered server (Microsoft Cluster Services) that is queried from 4 IIS6 Windows Server 2003 frontends. Each frontend runs both classic ASP apps connection with SQL Server ODBC and .NET2 apps connecting with System.Data.SqlClient. Ocassionaly we get a string of errors/timeouts opening a connection lasting maybe 2 minutes.
One the classic ASP apps we log one of these two errors:
Microsoft OLE DB Provider for ODBC Drivers (0x80004005) [Microsoft][ODBC SQL Server Driver][DBNETLIB]General network error. Check your network documentation
or
Microsoft OLE DB Provider for ODBC Drivers (0x80004005) [Microsoft][ODBC SQL Server Driver]Timeout expired on the ADODB.Connection.Open On the .NET2 apps we log Message Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
StackTrace at
System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject) at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) at System.Data.SqlClient.SqlConnection.Open() at System.Web.SessionState.SqlSessionStateStore.SqlStateConnection..ctor(SqlPartitionInfo sqlPartitionInfo)
I am learning SQL Server 2005 Express, and want to use the Northwind data base as used in many code examples. I wanted to attach the Northwind data base via SQL Management Studio, but cannot find a Northwind.mdf file.
When I do a search using 'Northwind', I see there are already a couple of different versions of Northwind already loaded. One appears to be associated with SQL Server Mobile Edition (Samples folder) and another seems to be associated with Visual Studio 8SDKv2.0Quickstart.
Can I use one of these existing Northwind databases (none have .mdf extention) for SQL Server 2005 or do I need to download yet another version?
I have sql server 2000 developer, sql server 2005 (workgroup, standard and enterprise), express and compact 3.5 and i need to test 2000, 2005 express and a full version of 2005 and compact all on the same machine.
Has anyone done something like this and are there any issues with this? i have seen some threads about 2000 and 2005 being fine as long as one is a default instance and one is a named instance. Would i be able to do the same with say express being the default instance and then 2000 and 2005 both having named instances? And is there a particular order i should install? I already have 2005 express as the default instance and compact installed already.
I have one publicacion on ms sql 2005 Enterprise w.sp1/MS Windows 2003 Enterprise w.sp2 and one subscriber on MS sql 2005 Enterprise w.sp1/MS Windows 2003 w.sp2, but I have also 3 subscriber on MS SQL 2000 w.sp3/MS Windows 2000 advanced server w.sp4. They replicate the same database with a publication compatible with 80RTM, All works fine with data replication, but I can't replicate DDL to MS sql 2005 suscriber, I don't care that don't replicate DDL, but I want manually alter triggers at MS sql 2005 suscriber, but I get this error at the subscriber on when I run the ALTER TRIGGER statement :
Msg 21531, Level 16, State 1, Procedure sp_MSmerge_altertrigger, Line 67
The DDL statement cannot be performed at the Subscriber or Republisher.
Msg 21530, Level 16, State 1, Procedure sp_MSmerge_ddldispatcher, Line 181
The DDL operation failed inside merge DDL replication manipulation.
Msg 3609, Level 16, State 2, Procedure TU_Centros_Distribucion_Articulos, Line 58
The transaction ended in the trigger. The batch has been aborted.
Any help will be appreciated,
PD. I miss sql2000 replication, where I have full control over the database logic
I just finished an OLEDB interface written in VS2005 C++ that works with Sql Server Compact Edition 3.1. My team now wants me to make my interface compatible with Sql Server 2000, 2005, and 2005 Express. My question is...what header/lib files do I need installed and in my stdafx.h to pull this off? Is there a particular order I need to include these files in?
Right now I'm just including the following for SSCE:
#include <ssceerr30.h>
#include <ssceoledb30.h>
Once I get the right includes figured out, the next step is figuring out what CLSID's I should use in the CoCreateInstance call. I *think* I'm supposed to use CLSID_SQLOLEDB for 2000, CLSID_SQLNCLI for 2005, and I haven't a clue for 2005 Express. I could use some clarification on this as well.
Thanks a ton in advance...I've always been impressed by the MSDN boards...
One of the big problems with the old MDAC was different versions on different client machines. You would test your app with the latest version say, but when you deployed it, it might fail as the client has a different version.
My company develops software for Municipal Government clients. These clients use other SQL Server applications as well as ours, but they can only use one version of the client software (MDAC) on a given desktop. That means if we require a particular MDAC version, but the clients other applications from other vendors don't officially support that MDAC version, the client is in a real jam.
Our software also supports Oracle, which allows our software to specify a particular Oracle Home which points to a directory with a particular version of the Oracle client dlls (along with corresponding registry entries for that Oracle Home), such that we control the exact client version of the Oracle software that the client uses with our applications. This will not interfere with, and is completely seperate, from the default Oracle home installed when you install the Oracle client software.
What I would like to see for the Native Client is the ability to have our applications use the version of the Native Client that we wish to support and deploy without interfering with the Native Client version used by other applications. Have a default Native Client, but allow applications to somehow specify a different Native Client version/set of DLLs.
Is there any such functionality with the Native Client? (I didn't see any mention of such in the documentation, but I thought I'd ask)
If not, are there any future plans to support multiple Native Client versions on the same desktop?
I currently have three SQL Server instances installed on my notebook. One is v8, which I believe is used by an accounting application. The other two are as follows:-
SQL Server MSSMLBIZ
SQL Server SQLEXPRESS
The second one (SQLEXPRESS) fails to start generating the following error:-
The SQL Server (SQLEXPRESS) service terminated with service-specific error 17058 (0x42A2).
Other services listed in SQL Server Configuration Manager are:-
SQL Server Integration Services - which runs apparently normally.
SQL Server Analysis Services (MSSQLSERVER)
SQL Server Reporting Services (MSSQLSERVER)
SQL Server Browser
The last thre of these are run under LocalSystem.
I have been trying to install the SQLServer SP2 to the SQLEXPRESS instance for some number of days now, but each time it runs, it fails to install.
I am beginning to wonder if there is a sequence of installation for each of the above instances that should be followed. Can anyone give me any suggestions, or answers to the above problems?
I know that the File connection can be used in the File system task and Flatfile connection can be used in Flat File source or destination, but I don't know which Task or Source/Destination can use the Multiple File connection and Multiple Flatfile connection. Thanks
I have this problem occuring intermittently:When I try to add a package to the project, and click on the Packagepath button. I get a oledb error x080004005 (client unable toestablish connection)...After I click ok, and click on the Package path again 2 or 3 times,the error goes away and I get the list of packages displayed. Sometime I get an empty list box.Similar to this happens when I execute a package also. When I executeit 2nd or 3 rd time it works fine. The error happens only when I amtrying to connect to the serverdatabase. Once it is in the databaseI do not get any error message.This is what I have:I have sql 2005 installed.Microsoft SQL Server ManagementStudio9.00.1399.00Microsoft Analysis Services ClientTools2005.090.1399.00Microsoft Data Access Components(MDAC)2000.085.1117.00 (xpsp_sp2_rtm.040803-2158)Thank you in advance!!!
When I try to add a package to the project, and click on the Package path button. I get a oledb error x080004005 (client unable to establish connection)...
After I click ok, and click on the Package path again 2 or 3 times, the error goes away and I get the list of packages displayed. Some time I get an empty list box.
Similar to this happens when I execute a package also. When I execute it 2nd or 3 rd time it works fine. The error happens only when I am trying to connect to the serverdatabase. Once it is in the database I do not get any error message.
This is what I have:
I have sql 2005 installed. Microsoft SQL Server Management Studio 9.00.1399.00 Microsoft Analysis Services Client Tools 2005.090.1399.00 Microsoft Data Access Components (MDAC) 2000.085.1117.00 (xpsp_sp2_rtm.040803-2158)
I have log shipping setup to 2 different servers. Every once in a while I get the
Server: Msg 3201, Level 16, State 1, Line 1 Cannot open backup device 'E:fac.dat'. Device error or device off-line. See the SQL Server error log for more details. Server: Msg 3013, Level 16, State 1, Line 1 Backup or restore operation terminating abnormally.
Checked MSDN which said it was a permissions error, which isn't right, because the same account works for this db and several others all the time. Anyone else seen this?
I've a SQL server that intermittently restarts itself mostly during. Its a SQL Server 6.5 SP4 running NT 4.0 SP6. It really has no rhyme or reason to it happening. The are no indications in either the SQL or the Nt events logs. Has anyone heard of this?
We recently migrated a SQL 2000 DB to SQL Server 2005 SP2. We have a VB 6 executable that uses the SQL Server 2005 DB. Immediately we began getting intermittent errors when trying to run a Stored Proc on SQL 2005 DB. The two errors we see are:
Timeout expired
[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.
If you immediately try to run the same query, it usually will work. The queries are random and so are the errors. I have gotten the time out error in Server Management Studio a couple of times.
In the VB 6 App we are using MDAC 2.81. Her is the connection string: Provider=SQLOLEDB.1;User ID=user;password=password;Initial Catalog=OASIS;Data Source=servername, portnumber
We added the port number to the DataSource in an attempt to troublshoot the issue, but it made no difference.
We have run sysinternals Process Monitor on a PC with the app running and we saw NAME NOT FOUND Results for Query Open actions for these DLLS: C:Program FilesOASISCLUSAPI.DLL C:Program FilesOASISRESUTILS.DLL C:Program FilesOASIStdsapi.dll
C:Program FilesOASIS is the application path. Of course, they are not in the application path but they are in C:WindowsSystem32. They do not seem to be registered.
Here is an example of the code we use in a class to run a SP:
Public Function FetchPostings() As ADODB.Recordset Dim cmFetch As ADODB.Command
On Error GoTo HandleError Set cmFetch = New ADODB.Command With cmFetch .Name = "FetchObligations" .ActiveConnection = gobjSecurity.Connection 'This is a connection string not a connection object .CommandText = "spClaimFetchObligations" .CommandType = adCmdStoredProc .Parameters.Append .CreateParameter("ClaimID", adInteger, adParamInput, , mlngClaimID) Set FetchObligations = .Execute End With
ExitSub: Set cmFetch = Nothing Exit Function
HandleError: gobjError.HandleError Err.Number, Err.Description, App.EXEName, "clsClaim", "FetchObligations", gobjSecurity.UserID Resume ExitSub End Function
I have VS 2005 and SQL CE 3.0. I sometimes get the a FileNotFoundException when I first use ExecuteReader. I believe this is because a dll has not been copied across because if I restart the emulator I can get it to work again.
Do I need to add a cab file/dll to my project to stop this happening?
I have developed a report that pulls its data from an SSAS cube. The report is grouped on Fields!FacilityName. On each "page" of the report, I have information for the displayed facility.
At the top of each page in my report I have a textbox whose value is =Fields!FacilityName. Further down on the report I have another text box whose value is set exactly the same. When I preview the report, I always have a value in the upper box, but only sometimes have a value in the lower box. If I change the value in the lower box to just a text string, it will always display, but when I put in the actual field reference it does not. It always doesn't display for the same facility names. Remember, the upper textbox on the form always displays 100% of the time.
I have a Dundas chart in the middle of the page on the report between these textboxes, but another field that pulls parameters and even a matrix all render correctly below that chart.
They both have the same parent according to the properties. I have even copied and pasted the working textbox further down the screen, with no improvement. When I changed the value of the textbox to "=cstr(len(Fields!FacilityName))", on the pages when it wants to be blank, it reads 0, and on other pages it shows a larger number. But the other textbox on the screen will always properly show the FacilityName.
I have also tried changing the name of the textbox, settings output to YES instead of Auto. If I slide the non-working textbox up to the top of the page and the working textbox down to the bottom area of the page, the bevavior switches.
Does anybody know of rendering issues with textboxes showing the same infomation?
We are using HTTPS anonymous merge subscriptions....
Sometimes when trying to synchonise, we will get the following error messages returned to the subscriber....
The upload message to be sent to Publisher '**thewebserver**' is being generated The merge process is using Exchange ID '0F65CFCB-AF17-47DC-8D98-493A44C243E0' for this web synchronization session. The Merge Agent could not connect to the URL 'https://**thewebserver**/client/replisapi.dll' during Web synchronization. Please verify that the URL, Internet login credentials and proxy server settings are correct and that the Web server is reachable. The Merge Agent could not connect to the URL 'https://**thewebserver**/client/replisapi.dll' during Web synchronization. Please verify that the URL, Internet login credentials and proxy server settings are correct and that the Web server is reachable. The Merge Agent received the following error status and message from the Internet Information Services (IIS) server during Web synchronization: [401 :'Unauthorized']. When troubleshooting, ensure that the Web synchronization settings for the subscription are correct, and increase the internet timeout setting at the Subscriber and the connection timeout at the Web server.
If I then go to a web brower, put in the HTTPS address, it brings up the logon dialog - I put in the admin username and password to confirm the connection and that's fine.
We try and synchronise again, and this time it works - it's as though I have 'woken' it up again and it's happy to play.
Is increasing the timeouts as suggested by the error message the way to go ? If so, where does one set the 'internet timeout setting at the subscriber', and the 'connection timeout at the webserver' ?
I currently run a nightly replication from a windows server 2003 machine with sql server 2000 sp3 to a windows 2003 server machine with sql server 2005 sp1. I run a snapshot replication as merge is not supported from 2000 to 2005.
2 out 5 snapshots weekly fail with the following error:
2006-08-09 17:00:06.97 Message Code: 10054 2006-08-09 17:00:06.97 2006-08-09 17:00:06.97 [0%] The replication agent had encountered an exception. 2006-08-09 17:00:06.97 Source: Replication 2006-08-09 17:00:06.97 Exception Type: Microsoft.SqlServer.Replication.ConnectionFailureException 2006-08-09 17:00:06.97 Exception Message: TCP Provider: An existing connection was forcibly closed by the remote host.
I have setup the sql server 2005 agent service to automatic with a 'log on as' domain admin account. The sql server agent on the 2000 machine uses the local system account.
I'm querying a small SQL2005 database and finding that the query can sometimes complete in under a second and then 5 minutes later the same query can take 15 minutes to complete.
The query I'm running is very simple as follows: select TOP 26 * from vSearchListOpportunityItem WHERE OpIt_OpportunityId=2495 ORDER BY Prod_Name, OpIt_OpportunityItemId
The view it is pulling data from only contains only 1890 lines, which in turn pulls data from 3 tables with 821, 2560, and 1957 lines of data. In other words it's small. I have noticed that if I try and open the smallest of these tables while on a 'go slow' period it also takes around 15 minutes to return the data.
The database was originally on SQL 2000. It is the only database on this powerful quad core server. The SQL Server CPU usage never goes above 40%, and always has free memory. No sign of locks.
I can't figure out why such a small database is going so slow with such a simple query. Any ideas?
After installing the Advanced Services package, I started getting errors connecting to a database (.MDF) that I've been using for weeks/months.
The error was something like "login failed for machineuser". After twiddling with the connection string and starting and stopping the SQLEXPRESS service it started working again. Did some more work, everything was fine, shutdown and went to bed.
This morning, I am unable to connect to the database - nor any other database, it seems. This time I'm getting "cannot find the physical file" type errors.
Any leads on solving this would be much appreciated. I've search using the error codes and I'm not turning anything up that seems quite like the problem I'm having.
I'm having weird issues with connecting to MS SQL Server. Sometimes it can establish a connection and sometimes it can't. This is both with ODBC and with .net code. This happens on multiple computers. I.e. one minute you can connect, the next you can't.
I have a SQL 2000 server which connects fine every time. So I assume the problem is with the upgraded MS SQL Server. I want to be able to resolve this issue before upgrading the main server to SQL 2005.
In an SSB test project created from the T-SQL batch in Stuart Padley's Weblog (subtitled "SQL Server 2005 stuff I couldn't find anywhere else", http://blogs.msdn.com/stuartpa/archive/2005/07/25/443229.aspx) I found strange inconsistencies with enquing messages between two databases on the same SQL Server 2005 Standard Edition SP-1 CTP March instance running under Windows Server 2003 SE SP-1:
Sending a simple message from the Initiator to the Target database with either the SendMessageProc stored procedure or its code as a batch fails for about 50% of all tries, with varying failure patters (up to 10 sequential attempts fail). Messages for failed tries remained in the transmission_queue, but didn't appear in the InitiatorQueue or TargetQueue.
I made the following changes to Stuart's code in the SendMessageProc procedure and my SendInitiatorToTarget.sql messaging script:
1. Split out EXEC SendMessageProc from Stage 4 and all of Stage 5 into a separate batch to enable sending multiple messages without recreating all objects. 2. Changed BEGIN DIALOG to BEGIN DIALOG CONVERSATION 3. Added a missing END CONVERSATION statement
A simple intradatabase service based on the "Hello World" DB Engine sample run in the Northwind or AdventureWorks database behaves as expected.
The partition with SQLS 2005 SP-1 also has SSX SP-1 with Advanced Services installed. Some minor problems occured when installing SSX SP-1, so I removed the original SSX instance and reinstalled SSX SP-1. See http://oakleafblog.blogspot.com/2006/03/sql-server-2005-sp1-ctp-available-for.html.
The same SSMS project runs fine on a fresh install of SQLS 2005 RTM under WS 2003 SP-1 on another machine partition. (This machine isn't running VS.) No messages fail to reach the Target database, as would be expected.
Has anyone else encountered similar anomalous behavior with SSB under SP-1 CTP? This problem ran me nuts for an entire day until I finally gave up and created a new SQLS 2005 RTM test instance.
If anyone (especially Remus) wants a copy of the scrpt, send your e-mail address to roger_jennings(nospam_at)compuserve(nospam_dot)com.
I have an ASP page that opens a recordset on a stored procedure. I've had it in production for over a year, and it usually works fine - subsecond response. However, in the past couple weeks, the recordset open command has intermittently started to return timeout errors. It's very strange: when the timeout occurs, it can be dependably reproduced by opening the ASP page with the same parameter that produced the initial timeout. However, if you pass a different parameter to the procedure, it runs fine! It only times out when using the specific parameter that produced the initial timeout.
Even stranger: If, when attempting to debug it, I use QA to run the sp with the "defective" parameter, the sp invariably runs fine! And subsequent runs of the ASP page start working as well!
I have repeated this process many times in the past couple weeks: receive a report of the timeout error; open the asp page with the parameter that produced the timeout to verify; repeat; open the asp page with a different parameter - works fine; repeat with the initial parameter - timeout; Open QA and run the sp - no problem; refresh the asp page - no more symptom.
The connection to the SQL Server (7.0) uses a specific SQL login for all communications with the server. So all asp pages are logged in under the same name. I thought this might be a connection pooliing issue, so this morning, when the problem occurred, I logged into QA as the special name, but again, there was no problem running the sp from QA.
So - I've run SQL Profiler to track what's going on when the problem occurs and I've discovered the last statement to successfully run. Here is the sp:
/* * File Name: np_GetAvailablePreviews.sql
Returns a list of "reports" available to be previewed, defined as:
date/shift combination with "P" mode and "C" status (if there are Shift records, there must be an All record)
If none exist, check for the existence of accepted (mode = "A") Shift records without a corresponding All record - if so, return an All item for that date
Concatenate <OPTION> tags around each item */
CREATE PROCEDURE np_GetAvailablePreviews ( @DivisionNumber smallint) AS BEGIN set nocount on declare @count int, @datefrom datetime select @datefrom = dateadd(day,-900,getdate()) CREATE TABLE #PreviewReports ( ProductionDate datetime NULL, Shift char(3) NULL )
Insert #PreviewReports SELECT DISTINCT ProductionDate,Shift FROM dbo.LineItems WHERE DivisionNumber = @DivisionNumber AND Mode = 'P' AND Status = 'C' AND productiondate >= @datefrom
-->>>The above command completes successfully according to Profiler
Insert #PreviewReports SELECT distinct t1.ProductionDate, 'All' FROM (SELECT distinct ProductionDate, Shift, Mode, Status FROM LineItems WHERE DivisionNumber = @DivisionNumber AND Shift<>'All' AND Mode='A' AND Status='C' AND productiondate >= @datefrom AND timeperiod IN ('Day','Shift') ) t1 LEFT JOIN (SELECT distinct ProductionDate, Shift, Mode, Status FROM LineItems WHERE DivisionNumber = @DivisionNumber AND Shift='All' AND Mode='A' AND Status='C' AND productiondate >= @datefrom AND timeperiod IN ('Day','Shift') ) t2 ON t1.ProductionDate = t2.ProductionDate WHERE t2.ProductionDate Is Null AND NOT EXISTS (Select * from #PreviewReports where productiondate = t1.ProductionDate and Shift = 'All')
-->>>This one (the one before this comment) starts, but does not -->>>complete
set @count=(Select Count(*) From #PreviewReports)
-->>This one never begins - the ADO command times out
<snipped>
I did not provide a repro script because the problem is so intermittent that I doubted it would do anyone any good.
However if someone feels they want to try to reproduce this, I will attempt to create a repro script for them.
I suspect there is an issue with the temp table, but it's such a moving target that I haven't been able to pin it down.
I am getting intermittent connectivity issues while connecting to a remote SQL Server 2000 database through the Enterprise Manager. It gives a time-out error
Initially I guessed it must be the network but then I was able to term-serv successfully into the remote server and work without any connectivity issues.
I have a SP that I use to insert records in a table. This SP is calledhundreds of times per minute.Most inserts complete very fast. And the profiler data is as follows:CPU: 0Reads: 10Writes: 1Duration: varies from 1 to 30But once in a while the insert SP seems to stall and takes a very longtime. Here's the info returned by profiles in this case:CPU: 0Reads: 10Writes: 1Duration: can vary from 6000 to 60000Note that the CPU, reads, writes remain the same. But the duration ofthe SP increases. What could be the reason for this?? The SPeventually completes in all cases - its just that they seem to take avery long time sometimes??What areas should I investigate??Thanks in advance,DK
