|
sql
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
SQL Timeout Error
I just created a View, and when I tried to run it, I received the following error message: error message: timeout expired. the timeout elapsed prior to completion of the operation or the server is not responding. error source: .Net SqlClient Data Provider When I researched the above error message via Google, the solution is to run the CommandTimeout, and I don't know how to run it. First of, if the CommandTimeout is the solution to the error, can you tell me how to run it? If the CommandTimeout is not the solution, can you help me with the error? Thanks. You may want to run the query in SQL Server Management Studio first to see
how long it may take and what its query plan looks like. This can help you decide what might be a CommandTimeout setting or perhaps you need to optimize your view so that it completes within the current timeout threshold. As always, it helps to clarify how you actually ran it. Linchi Show quoteHide quote "Accesshelp" wrote: > Good morning all, > > I just created a View, and when I tried to run it, I received the following > error message: > > error message: timeout expired. the timeout elapsed prior to completion of > the operation or the server is not responding. > > error source: .Net SqlClient Data Provider > > When I researched the above error message via Google, the solution is to run > the CommandTimeout, and I don't know how to run it. > > First of, if the CommandTimeout is the solution to the error, can you tell > me how to run it? > > If the CommandTimeout is not the solution, can you help me with the error? > > Thanks. Hi Linchi,
Thanks for your response. I ran the Select query as you said, and it took 1:34 minutes. The outputs are 1 column and 133 rows. I am not sure what you mean by "to clarify how you actually ran it" (sorry I am still new to SQL Server). First of all, I do everything in SQL Server Management Studio Express. I went to Views section of the database and created a View (just like creating a Select query). Then I click on Execute SQL from the right-click dropdown menu. By the way, how or where do I set the CommandTimeout? Thanks. Show quoteHide quote "Linchi Shea" wrote: > You may want to run the query in SQL Server Management Studio first to see > how long it may take and what its query plan looks like. This can help you > decide what might be a CommandTimeout setting or perhaps you need to optimize > your view so that it completes within the current timeout threshold. > > As always, it helps to clarify how you actually ran it. > > Linchi > > "Accesshelp" wrote: > > > Good morning all, > > > > I just created a View, and when I tried to run it, I received the following > > error message: > > > > error message: timeout expired. the timeout elapsed prior to completion of > > the operation or the server is not responding. > > > > error source: .Net SqlClient Data Provider > > > > When I researched the above error message via Google, the solution is to run > > the CommandTimeout, and I don't know how to run it. > > > > First of, if the CommandTimeout is the solution to the error, can you tell > > me how to run it? > > > > If the CommandTimeout is not the solution, can you help me with the error? > > > > Thanks. > I am not sure what you mean by "to clarify how you actually ran it" (sorry I From your initial description, it appeared that you were developing a .NET app. In that case, you just needed to set the System.Data.SqlClient.SqlCommand.CommandTimeout property. Now, that doesn't appear to be the case. I don't use Management Studio Express. But in Management Studio, you can go Tools --> Options --> Query Execution --> SQL Server --> General to set query exeution timeout. 0 means no timeout. I don't know what governs the timeout when you click on Execute SQL from the right-click dropdown menu of a view. Someone else may be able to chime in. Linchi Show quoteHide quote "Accesshelp" wrote: > Hi Linchi, > > Thanks for your response. I ran the Select query as you said, and it took > 1:34 minutes. The outputs are 1 column and 133 rows. > > I am not sure what you mean by "to clarify how you actually ran it" (sorry I > am still new to SQL Server). First of all, I do everything in SQL Server > Management Studio Express. I went to Views section of the database and > created a View (just like creating a Select query). Then I click on Execute > SQL from the right-click dropdown menu. > > By the way, how or where do I set the CommandTimeout? > > Thanks. > > "Linchi Shea" wrote: > > > You may want to run the query in SQL Server Management Studio first to see > > how long it may take and what its query plan looks like. This can help you > > decide what might be a CommandTimeout setting or perhaps you need to optimize > > your view so that it completes within the current timeout threshold. > > > > As always, it helps to clarify how you actually ran it. > > > > Linchi > > > > "Accesshelp" wrote: > > > > > Good morning all, > > > > > > I just created a View, and when I tried to run it, I received the following > > > error message: > > > > > > error message: timeout expired. the timeout elapsed prior to completion of > > > the operation or the server is not responding. > > > > > > error source: .Net SqlClient Data Provider > > > > > > When I researched the above error message via Google, the solution is to run > > > the CommandTimeout, and I don't know how to run it. > > > > > > First of, if the CommandTimeout is the solution to the error, can you tell > > > me how to run it? > > > > > > If the CommandTimeout is not the solution, can you help me with the error? > > > > > > Thanks. Linchi,
I am using Express versions of SQL Server 2005 and SQL Server Management Studio. I went to Tools --> Options --> Query Execution --> SQL Server --> General and saw 0 second for execution time-out. I think regular and express version have the same settings, except express does not have services (integration services, etc.) like regular does. In addition, my SQL Server 2005 Express is installed on hard drive, not on the network/server. I don't know those information would be matter. Thanks again for your helps. Show quoteHide quote "Linchi Shea" wrote: > > I am not sure what you mean by "to clarify how you actually ran it" (sorry I > > From your initial description, it appeared that you were developing a .NET > app. In that case, you just needed to set the > System.Data.SqlClient.SqlCommand.CommandTimeout property. Now, that doesn't > appear to be the case. > > I don't use Management Studio Express. But in Management Studio, you can go > Tools --> Options --> Query Execution --> SQL Server --> General to set query > exeution timeout. 0 means no timeout. > > I don't know what governs the timeout when you click on Execute SQL from the > right-click dropdown menu of a view. Someone else may be able to chime in. > > Linchi > > "Accesshelp" wrote: > > > Hi Linchi, > > > > Thanks for your response. I ran the Select query as you said, and it took > > 1:34 minutes. The outputs are 1 column and 133 rows. > > > > I am not sure what you mean by "to clarify how you actually ran it" (sorry I > > am still new to SQL Server). First of all, I do everything in SQL Server > > Management Studio Express. I went to Views section of the database and > > created a View (just like creating a Select query). Then I click on Execute > > SQL from the right-click dropdown menu. > > > > By the way, how or where do I set the CommandTimeout? > > > > Thanks. > > > > "Linchi Shea" wrote: > > > > > You may want to run the query in SQL Server Management Studio first to see > > > how long it may take and what its query plan looks like. This can help you > > > decide what might be a CommandTimeout setting or perhaps you need to optimize > > > your view so that it completes within the current timeout threshold. > > > > > > As always, it helps to clarify how you actually ran it. > > > > > > Linchi > > > > > > "Accesshelp" wrote: > > > > > > > Good morning all, > > > > > > > > I just created a View, and when I tried to run it, I received the following > > > > error message: > > > > > > > > error message: timeout expired. the timeout elapsed prior to completion of > > > > the operation or the server is not responding. > > > > > > > > error source: .Net SqlClient Data Provider > > > > > > > > When I researched the above error message via Google, the solution is to run > > > > the CommandTimeout, and I don't know how to run it. > > > > > > > > First of, if the CommandTimeout is the solution to the error, can you tell > > > > me how to run it? > > > > > > > > If the CommandTimeout is not the solution, can you help me with the error? > > > > > > > > Thanks. Hi, AccessHelp
If you are using .net client app to select data from the view, check the following: 1. Whether SqlConnection object establishes connection to the sql server successfully - check ConnectionString, ConnectionTimeout property (default = 15 sec) 2. If the connection was established, you may need to set the CommandTimeout property of the SqlCommand object to a value > 30 sec (default = 30 sec) Robert Lakinski Show quoteHide quote "Accesshelp" <Accessh***@discussions.microsoft.com> wrote in message news:8C19B329-0148-4EDE-A1EC-A2E3A3674C47@microsoft.com... > Good morning all, > > I just created a View, and when I tried to run it, I received the > following > error message: > > error message: timeout expired. the timeout elapsed prior to completion > of > the operation or the server is not responding. > > error source: .Net SqlClient Data Provider > > When I researched the above error message via Google, the solution is to > run > the CommandTimeout, and I don't know how to run it. > > First of, if the CommandTimeout is the solution to the error, can you tell > me how to run it? > > If the CommandTimeout is not the solution, can you help me with the error? > > Thanks. Robert,
Thanks for your response. How can I check whether SqlConnection object is estiablished, and how do I set the CommandTimeout property? I am sorry I am still new to SQL Server. Thanks. Show quoteHide quote "Robert Lakinski" wrote: > Hi, AccessHelp > > If you are using .net client app to select data from the view, check the > following: > > 1. Whether SqlConnection object establishes connection to the sql server > successfully - check ConnectionString, ConnectionTimeout property (default > = 15 sec) > 2. If the connection was established, you may need to set the CommandTimeout > property of the SqlCommand object to a value > 30 sec (default = 30 sec) > > Robert Lakinski > > "Accesshelp" <Accessh***@discussions.microsoft.com> wrote in message > news:8C19B329-0148-4EDE-A1EC-A2E3A3674C47@microsoft.com... > > Good morning all, > > > > I just created a View, and when I tried to run it, I received the > > following > > error message: > > > > error message: timeout expired. the timeout elapsed prior to completion > > of > > the operation or the server is not responding. > > > > error source: .Net SqlClient Data Provider > > > > When I researched the above error message via Google, the solution is to > > run > > the CommandTimeout, and I don't know how to run it. > > > > First of, if the CommandTimeout is the solution to the error, can you tell > > me how to run it? > > > > If the CommandTimeout is not the solution, can you help me with the error? > > > > Thanks. > > > Thanks for your response. How can I check whether SqlConnection object is By debugging your .net client application. Can you post some code?> estiablished Which version of Visual Studio are you using ? What kind of data access objects are you using: SqlDataSource, SqlDataAdapter or SqlCommand, linq ...? Robert Lakinski , and how do I set the CommandTimeout property? I am sorry I am Show quoteHide quote > still new to SQL Server. > > Thanks. > > "Robert Lakinski" wrote: > >> Hi, AccessHelp >> >> If you are using .net client app to select data from the view, check the >> following: >> >> 1. Whether SqlConnection object establishes connection to the sql server >> successfully - check ConnectionString, ConnectionTimeout property >> (default >> = 15 sec) >> 2. If the connection was established, you may need to set the >> CommandTimeout >> property of the SqlCommand object to a value > 30 sec (default = 30 sec) >> >> Robert Lakinski >> >> "Accesshelp" <Accessh***@discussions.microsoft.com> wrote in message >> news:8C19B329-0148-4EDE-A1EC-A2E3A3674C47@microsoft.com... >> > Good morning all, >> > >> > I just created a View, and when I tried to run it, I received the >> > following >> > error message: >> > >> > error message: timeout expired. the timeout elapsed prior to >> > completion >> > of >> > the operation or the server is not responding. >> > >> > error source: .Net SqlClient Data Provider >> > >> > When I researched the above error message via Google, the solution is >> > to >> > run >> > the CommandTimeout, and I don't know how to run it. >> > >> > First of, if the CommandTimeout is the solution to the error, can you >> > tell >> > me how to run it? >> > >> > If the CommandTimeout is not the solution, can you help me with the >> > error? >> > >> > Thanks. >> >> AccessHelp,
If you are NOT trying to access the data in the view via your own developed ..Net application (using VS or other tool), ignore my posts. Robert Show quoteHide quote "Robert Lakinski" <rlakin***@gmail.com> wrote in message news:uyHMRzB9JHA.4560@TK2MSFTNGP03.phx.gbl... > >> Thanks for your response. How can I check whether SqlConnection object >> is >> estiablished > > By debugging your .net client application. Can you post some code? > Which version of Visual Studio are you using ? > What kind of data access objects are you using: SqlDataSource, > SqlDataAdapter or SqlCommand, linq ...? > > Robert Lakinski > > > , and how do I set the CommandTimeout property? I am sorry I am >> still new to SQL Server. >> >> Thanks. >> >> "Robert Lakinski" wrote: >> >>> Hi, AccessHelp >>> >>> If you are using .net client app to select data from the view, check the >>> following: >>> >>> 1. Whether SqlConnection object establishes connection to the sql server >>> successfully - check ConnectionString, ConnectionTimeout property >>> (default >>> = 15 sec) >>> 2. If the connection was established, you may need to set the >>> CommandTimeout >>> property of the SqlCommand object to a value > 30 sec (default = 30 sec) >>> >>> Robert Lakinski >>> >>> "Accesshelp" <Accessh***@discussions.microsoft.com> wrote in message >>> news:8C19B329-0148-4EDE-A1EC-A2E3A3674C47@microsoft.com... >>> > Good morning all, >>> > >>> > I just created a View, and when I tried to run it, I received the >>> > following >>> > error message: >>> > >>> > error message: timeout expired. the timeout elapsed prior to >>> > completion >>> > of >>> > the operation or the server is not responding. >>> > >>> > error source: .Net SqlClient Data Provider >>> > >>> > When I researched the above error message via Google, the solution is >>> > to >>> > run >>> > the CommandTimeout, and I don't know how to run it. >>> > >>> > First of, if the CommandTimeout is the solution to the error, can you >>> > tell >>> > me how to run it? >>> > >>> > If the CommandTimeout is not the solution, can you help me with the >>> > error? >>> > >>> > Thanks. >>> >>> > Robert,
First of all, I want to thank you for continuing to help me. Secondly, I want to use View as a Select query to access data in SQL from Access. From what I learned, I can not link between SQL and Access with regular SQL Select query. On the other hand, I can link between SQL and Access via View to access data. I just linked in Access to the View that I created in SQL via ODBC (as a linked table in Access), and I was able to open that linked table in Access and retrieve data. Somehow, if I try to open the View in SQL, I got that error message. I don't know why I got the error message. Thanks. Show quoteHide quote "Robert Lakinski" wrote: > AccessHelp, > > If you are NOT trying to access the data in the view via your own developed > ..Net application (using VS or other tool), ignore my posts. > > Robert > > "Robert Lakinski" <rlakin***@gmail.com> wrote in message > news:uyHMRzB9JHA.4560@TK2MSFTNGP03.phx.gbl... > > > >> Thanks for your response. How can I check whether SqlConnection object > >> is > >> estiablished > > > > By debugging your .net client application. Can you post some code? > > Which version of Visual Studio are you using ? > > What kind of data access objects are you using: SqlDataSource, > > SqlDataAdapter or SqlCommand, linq ...? > > > > Robert Lakinski > > > > > > , and how do I set the CommandTimeout property? I am sorry I am > >> still new to SQL Server. > >> > >> Thanks. > >> > >> "Robert Lakinski" wrote: > >> > >>> Hi, AccessHelp > >>> > >>> If you are using .net client app to select data from the view, check the > >>> following: > >>> > >>> 1. Whether SqlConnection object establishes connection to the sql server > >>> successfully - check ConnectionString, ConnectionTimeout property > >>> (default > >>> = 15 sec) > >>> 2. If the connection was established, you may need to set the > >>> CommandTimeout > >>> property of the SqlCommand object to a value > 30 sec (default = 30 sec) > >>> > >>> Robert Lakinski > >>> > >>> "Accesshelp" <Accessh***@discussions.microsoft.com> wrote in message > >>> news:8C19B329-0148-4EDE-A1EC-A2E3A3674C47@microsoft.com... > >>> > Good morning all, > >>> > > >>> > I just created a View, and when I tried to run it, I received the > >>> > following > >>> > error message: > >>> > > >>> > error message: timeout expired. the timeout elapsed prior to > >>> > completion > >>> > of > >>> > the operation or the server is not responding. > >>> > > >>> > error source: .Net SqlClient Data Provider > >>> > > >>> > When I researched the above error message via Google, the solution is > >>> > to > >>> > run > >>> > the CommandTimeout, and I don't know how to run it. > >>> > > >>> > First of, if the CommandTimeout is the solution to the error, can you > >>> > tell > >>> > me how to run it? > >>> > > >>> > If the CommandTimeout is not the solution, can you help me with the > >>> > error? > >>> > > >>> > Thanks. > >>> > >>> > > > > Hi Accesshelp,
Now I understand what you are trying to achieve. I'm not MS Access expert, but you can access data in Sql server via MS Access client application in two ways: - By linking tables. This approach is not limited to linking Sql Server views as a linked tables in MS Access. You can also link Sql Server tables as a linked tables in MS Access. - By using pass-through queries ( using T-Sql ) . This approach is usually more efficient. You can also check these guides: http://www.mssqltips.com/tip.asp?tip=1480 http://www.mssqltips.com/tip.asp?tip=1482 Regarding the problem related to your initial error while opening the view in Sql Server Management Studio Express, I have no idea what the problem could be - Tools/ Options / ..... Execution Timeout = 0 means 'wait forever'. But it seems that someone else has also experienced similar problem. Check this thread: http://www.eggheadcafe.com/conversation.aspx?messageid=33740922&threadid=33740922 Robert Show quoteHide quote "Accesshelp" <Accessh***@discussions.microsoft.com> wrote in message news:554730B6-B934-41D1-8960-E81C256ECC60@microsoft.com... > Robert, > > First of all, I want to thank you for continuing to help me. > > Secondly, I want to use View as a Select query to access data in SQL from > Access. From what I learned, I can not link between SQL and Access with > regular SQL Select query. On the other hand, I can link between SQL and > Access via View to access data. > > I just linked in Access to the View that I created in SQL via ODBC (as a > linked table in Access), and I was able to open that linked table in > Access > and retrieve data. Somehow, if I try to open the View in SQL, I got that > error message. > > I don't know why I got the error message. > > Thanks. > > "Robert Lakinski" wrote: > >> AccessHelp, >> >> If you are NOT trying to access the data in the view via your own >> developed >> ..Net application (using VS or other tool), ignore my posts. >> >> Robert >> >> "Robert Lakinski" <rlakin***@gmail.com> wrote in message >> news:uyHMRzB9JHA.4560@TK2MSFTNGP03.phx.gbl... >> > >> >> Thanks for your response. How can I check whether SqlConnection >> >> object >> >> is >> >> estiablished >> > >> > By debugging your .net client application. Can you post some code? >> > Which version of Visual Studio are you using ? >> > What kind of data access objects are you using: SqlDataSource, >> > SqlDataAdapter or SqlCommand, linq ...? >> > >> > Robert Lakinski >> > >> > >> > , and how do I set the CommandTimeout property? I am sorry I am >> >> still new to SQL Server. >> >> >> >> Thanks. >> >> >> >> "Robert Lakinski" wrote: >> >> >> >>> Hi, AccessHelp >> >>> >> >>> If you are using .net client app to select data from the view, check >> >>> the >> >>> following: >> >>> >> >>> 1. Whether SqlConnection object establishes connection to the sql >> >>> server >> >>> successfully - check ConnectionString, ConnectionTimeout property >> >>> (default >> >>> = 15 sec) >> >>> 2. If the connection was established, you may need to set the >> >>> CommandTimeout >> >>> property of the SqlCommand object to a value > 30 sec (default = 30 >> >>> sec) >> >>> >> >>> Robert Lakinski >> >>> >> >>> "Accesshelp" <Accessh***@discussions.microsoft.com> wrote in message >> >>> news:8C19B329-0148-4EDE-A1EC-A2E3A3674C47@microsoft.com... >> >>> > Good morning all, >> >>> > >> >>> > I just created a View, and when I tried to run it, I received the >> >>> > following >> >>> > error message: >> >>> > >> >>> > error message: timeout expired. the timeout elapsed prior to >> >>> > completion >> >>> > of >> >>> > the operation or the server is not responding. >> >>> > >> >>> > error source: .Net SqlClient Data Provider >> >>> > >> >>> > When I researched the above error message via Google, the solution >> >>> > is >> >>> > to >> >>> > run >> >>> > the CommandTimeout, and I don't know how to run it. >> >>> > >> >>> > First of, if the CommandTimeout is the solution to the error, can >> >>> > you >> >>> > tell >> >>> > me how to run it? >> >>> > >> >>> > If the CommandTimeout is not the solution, can you help me with the >> >>> > error? >> >>> > >> >>> > Thanks. >> >>> >> >>> >> > >> >> Good morning Robert,
I read the messages from the eggheadcafe link that you posted below, and I have all the settings (Execution time-out = 0 and Set Lock Timeout = -1 millseconds) that should have been the solutions. Unfortunately, I am still getting error when I run the View, but I do not get an error when I open that View in Access as linked table. I am able to open it. That is what puzzles me. I am getting error on opening View because of the # of records in the source table? The source table has over 10 million records. I think it is due to the # of records because I just ran a View on a source table with much fewer records than the first one, and I got the results with no error. Thanks. Show quoteHide quote "Robert Lakinski" wrote: > Hi Accesshelp, > > Now I understand what you are trying to achieve. > > I'm not MS Access expert, but you can access data in Sql server via MS > Access client application in two ways: > - By linking tables. This approach is not limited to linking Sql Server > views as a linked tables in MS Access. You can also link Sql Server tables > as a linked tables in MS Access. > - By using pass-through queries ( using T-Sql ) . This approach is > usually more efficient. > > You can also check these guides: > http://www.mssqltips.com/tip.asp?tip=1480 > http://www.mssqltips.com/tip.asp?tip=1482 > > > Regarding the problem related to your initial error while opening the view > in Sql Server Management Studio Express, > I have no idea what the problem could be - Tools/ Options / ..... > Execution Timeout = 0 means 'wait forever'. > But it seems that someone else has also experienced similar problem. > > Check this thread: > > http://www.eggheadcafe.com/conversation.aspx?messageid=33740922&threadid=33740922 > > > Robert > > "Accesshelp" <Accessh***@discussions.microsoft.com> wrote in message > news:554730B6-B934-41D1-8960-E81C256ECC60@microsoft.com... > > Robert, > > > > First of all, I want to thank you for continuing to help me. > > > > Secondly, I want to use View as a Select query to access data in SQL from > > Access. From what I learned, I can not link between SQL and Access with > > regular SQL Select query. On the other hand, I can link between SQL and > > Access via View to access data. > > > > I just linked in Access to the View that I created in SQL via ODBC (as a > > linked table in Access), and I was able to open that linked table in > > Access > > and retrieve data. Somehow, if I try to open the View in SQL, I got that > > error message. > > > > I don't know why I got the error message. > > > > Thanks. > > > > "Robert Lakinski" wrote: > > > >> AccessHelp, > >> > >> If you are NOT trying to access the data in the view via your own > >> developed > >> ..Net application (using VS or other tool), ignore my posts. > >> > >> Robert > >> > >> "Robert Lakinski" <rlakin***@gmail.com> wrote in message > >> news:uyHMRzB9JHA.4560@TK2MSFTNGP03.phx.gbl... > >> > > >> >> Thanks for your response. How can I check whether SqlConnection > >> >> object > >> >> is > >> >> estiablished > >> > > >> > By debugging your .net client application. Can you post some code? > >> > Which version of Visual Studio are you using ? > >> > What kind of data access objects are you using: SqlDataSource, > >> > SqlDataAdapter or SqlCommand, linq ...? > >> > > >> > Robert Lakinski > >> > > >> > > >> > , and how do I set the CommandTimeout property? I am sorry I am > >> >> still new to SQL Server. > >> >> > >> >> Thanks. > >> >> > >> >> "Robert Lakinski" wrote: > >> >> > >> >>> Hi, AccessHelp > >> >>> > >> >>> If you are using .net client app to select data from the view, check > >> >>> the > >> >>> following: > >> >>> > >> >>> 1. Whether SqlConnection object establishes connection to the sql > >> >>> server > >> >>> successfully - check ConnectionString, ConnectionTimeout property > >> >>> (default > >> >>> = 15 sec) > >> >>> 2. If the connection was established, you may need to set the > >> >>> CommandTimeout > >> >>> property of the SqlCommand object to a value > 30 sec (default = 30 > >> >>> sec) > >> >>> > >> >>> Robert Lakinski > >> >>> > >> >>> "Accesshelp" <Accessh***@discussions.microsoft.com> wrote in message > >> >>> news:8C19B329-0148-4EDE-A1EC-A2E3A3674C47@microsoft.com... > >> >>> > Good morning all, > >> >>> > > >> >>> > I just created a View, and when I tried to run it, I received the > >> >>> > following > >> >>> > error message: > >> >>> > > >> >>> > error message: timeout expired. the timeout elapsed prior to > >> >>> > completion > >> >>> > of > >> >>> > the operation or the server is not responding. > >> >>> > > >> >>> > error source: .Net SqlClient Data Provider > >> >>> > > >> >>> > When I researched the above error message via Google, the solution > >> >>> > is > >> >>> > to > >> >>> > run > >> >>> > the CommandTimeout, and I don't know how to run it. > >> >>> > > >> >>> > First of, if the CommandTimeout is the solution to the error, can > >> >>> > you > >> >>> > tell > >> >>> > me how to run it? > >> >>> > > >> >>> > If the CommandTimeout is not the solution, can you help me with the > >> >>> > error? > >> >>> > > >> >>> > Thanks. > >> >>> > >> >>> > >> > > >> > >> > > Robert,
First of all, I am using Express versions of SQL Server 2005 and SQL Server Management Studio. Currently, SQL Server 2005 Express is installed on my hard drive. I am just playing around with it while I am waiting for my IT department to create a regular version of SQL Server 2005 for me. Therefore, I don't think I have a .net client application. If I do, where do I go to debug it? Plus, I don't think I have the things (SqlDataSource, etc.) that you are asking for. If I do, where can I find them? I don't know it will relate to what you are looking for. When I finish with this project, I will have SQL Server as my back-end database and Access as my front-end database. Below is the code for my View that I am getting the error: USE [Database] GO /****** Object: View [dbo].[View] Script Date: 06/23/2009 13:12:02 ******/ SET ANSI_NULLS ON GO SET QUOTED_IDENTIFIER ON GO ALTER VIEW [dbo].[View] AS SELECT tblField FROM dbo.Table GROUP BY tblField Thank you for your helps and your patience. Show quoteHide quote "Robert Lakinski" wrote: > > > Thanks for your response. How can I check whether SqlConnection object is > > estiablished > > By debugging your .net client application. Can you post some code? > Which version of Visual Studio are you using ? > What kind of data access objects are you using: SqlDataSource, > SqlDataAdapter or SqlCommand, linq ...? > > Robert Lakinski > > > , and how do I set the CommandTimeout property? I am sorry I am > > still new to SQL Server. > > > > Thanks. > > > > "Robert Lakinski" wrote: > > > >> Hi, AccessHelp > >> > >> If you are using .net client app to select data from the view, check the > >> following: > >> > >> 1. Whether SqlConnection object establishes connection to the sql server > >> successfully - check ConnectionString, ConnectionTimeout property > >> (default > >> = 15 sec) > >> 2. If the connection was established, you may need to set the > >> CommandTimeout > >> property of the SqlCommand object to a value > 30 sec (default = 30 sec) > >> > >> Robert Lakinski > >> > >> "Accesshelp" <Accessh***@discussions.microsoft.com> wrote in message > >> news:8C19B329-0148-4EDE-A1EC-A2E3A3674C47@microsoft.com... > >> > Good morning all, > >> > > >> > I just created a View, and when I tried to run it, I received the > >> > following > >> > error message: > >> > > >> > error message: timeout expired. the timeout elapsed prior to > >> > completion > >> > of > >> > the operation or the server is not responding. > >> > > >> > error source: .Net SqlClient Data Provider > >> > > >> > When I researched the above error message via Google, the solution is > >> > to > >> > run > >> > the CommandTimeout, and I don't know how to run it. > >> > > >> > First of, if the CommandTimeout is the solution to the error, can you > >> > tell > >> > me how to run it? > >> > > >> > If the CommandTimeout is not the solution, can you help me with the > >> > error? > >> > > >> > Thanks. > >> > >> > >  
Other interesting topics
Multiple databases performance
Can I script out SQL Server jobs programmatically? Sql transaction log size because of reindexing setup a sql login which can only reset password kill the long run job automatically collation for multiple language in a column Identifying Memory Pressures understanding metrics/performance Replication syncobj views Creating table |
|||||||||||||||||||||||
