Sign In
MSDN Blogs
Microsoft Blog Images
More ...
July, 2008
Common Tasks
Blog Home
About
RSS for comments
RSS for posts
Atom
Search
Advanced search options...
Search In:
Everything
Blogs
Forums
People
Groups
Places
Pages
Date range:
All Time
Last Year
Last 6 Months
Last 3 Months
Last Month
Last Week
Last Two Days
Recent Posts
Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
Posted
over 4 years ago
by
Michael Aspengren - MSFT
Invalid attempt to read when no data is present.
Posted
over 4 years ago
by
Michael Aspengren - MSFT
Remote debugging of CLR Stored Procedures, two common errors and the reason behind them.
Posted
over 4 years ago
by
Michael Aspengren - MSFT
OLE DB provider "MICROSOFT.JET.OLEDB.4.0" for linked server "(null)" returned message "Unspecified error".
Posted
over 4 years ago
by
Michael Aspengren - MSFT
The simplification of JOIN. Simple example of how T-SQL JOIN work
Posted
over 4 years ago
by
Michael Aspengren - MSFT
Blogs I read
Fabulous Adventures In Coding
If broken it is, fix it you should
SQL in Stockholm
SQL Protocols
Tags
Access
ADO
ADO.Net
BID
CLR
Data Provider
Data Reader
Exception
Linked Server
LINQ to SQL
Login
ODBC
OleDb
Oracle
OracleClient
Remote Debugging
sqlcmd
SqlException
sqlncli
TCP
Timeout
t-sql
WCF
Windbg
Xml
Archives
Archives
February 2012
(1)
January 2012
(2)
December 2011
(1)
November 2011
(1)
October 2011
(3)
June 2011
(2)
May 2011
(1)
March 2011
(2)
February 2011
(1)
January 2011
(1)
December 2010
(2)
November 2010
(2)
October 2010
(2)
June 2010
(1)
May 2010
(3)
April 2010
(2)
March 2010
(4)
February 2010
(3)
January 2010
(4)
December 2009
(6)
November 2009
(3)
October 2009
(4)
September 2009
(7)
August 2009
(4)
July 2009
(3)
June 2009
(2)
May 2009
(3)
April 2009
(3)
March 2009
(4)
February 2009
(4)
January 2009
(2)
December 2008
(6)
November 2008
(3)
October 2008
(3)
September 2008
(6)
August 2008
(3)
July 2008
(9)
July, 2008
Common tips and tricks from a SQL Developer Support perspective
While some cases may start of as complex, they sometimes turn out to be caused by something not that complex. As the case always is once you have the solution. So I thought I would share some of the things that I've come across, and hopefully tha
RSS for posts
Subscribe via RSS
Sort by:
Most Recent
|
Most Views
|
Most Comments
Excerpt View
|
Full Post View
Common tips and tricks from a SQL Developer Support perspective
Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
Posted
over 4 years ago
by
Michael Aspengren - MSFT
3
Comments
The Scenario: Sometimes you may get a timeout issue looking something like this: System.Data.SqlClient.SqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. at System...
Common tips and tricks from a SQL Developer Support perspective
Invalid attempt to read when no data is present.
Posted
over 4 years ago
by
Michael Aspengren - MSFT
2
Comments
A short one. You are reading data from a data reader, and sometimes you hit: Invalid attempt to read when no data is present. It may seem obvious, but there have been occasions where this error is reported. When checking the code...
Common tips and tricks from a SQL Developer Support perspective
Remote debugging of CLR Stored Procedures, two common errors and the reason behind them.
Posted
over 4 years ago
by
Michael Aspengren - MSFT
1
Comments
The Scenario: You are attempting to remotely debug a CLR stored procedure from Visual Studio 2008. The Setup: Both debugger (VS 2008) and debugger target (Sql Server) is in the same domain but on different machines, which is a given, otherwise...
Common tips and tricks from a SQL Developer Support perspective
OLE DB provider "MICROSOFT.JET.OLEDB.4.0" for linked server "(null)" returned message "Unspecified error".
Posted
over 4 years ago
by
Michael Aspengren - MSFT
13
Comments
The scenario: You want to use a linked server (directly or indirectly) in SQL Server using the OleDb provider. With this provider you wish to use, for example, the OPENROWSET query against a file of some sort, *.txt, *.csv, *.xls, etc. The...
Common tips and tricks from a SQL Developer Support perspective
The simplification of JOIN. Simple example of how T-SQL JOIN work
Posted
over 4 years ago
by
Michael Aspengren - MSFT
1
Comments
Today I’ll try to explain how Joins work. If you are a DBA or a T-SQL expert, this is no news to you. But I’m not, and I’m sure there is a lot of people out there who are in the same situation. For example, sometimes there may be problems and...
Common tips and tricks from a SQL Developer Support perspective
Failed to find or load the registered .Net Framework Data Provider
Posted
over 4 years ago
by
Michael Aspengren - MSFT
1
Comments
When using a 3rd party .Net data provider. Or when you dynamically load a .Net provider you may get the following error: Failed to find or load the registered .Net Framework Data Provider There does not seem to be that much information about...
Common tips and tricks from a SQL Developer Support perspective
{"Syntax error in FROM clause."} when using text based datasources
Posted
over 4 years ago
by
Michael Aspengren - MSFT
0
Comments
This is also one of the issues that I have seen a few times. What happens here is that customer uses *.csv or *.xls or any text file as a data source and connects to it using .Net and OleDb. The error reported from the framework when issuing...
Common tips and tricks from a SQL Developer Support perspective
Creating a new system DSN: "Faulting application odbcad32.exe, version 3.526.3959.0, faulting module unknown, version 0.0.0.0, fault address 0x5bb312de"
Posted
over 4 years ago
by
Michael Aspengren - MSFT
2
Comments
This is an issue that I have seen a few times, so it could be worth mentioning. The error is as follows: When trying to create a new System DSN using the ODBC Data Source Administrator, the odbcad32.exe process goes down. And you will see...
Common tips and tricks from a SQL Developer Support perspective
Error/Event 18456 explained
Posted
over 4 years ago
by
Michael Aspengren - MSFT
0
Comments
Sometimes you may experience that your application, stand alone or web, can't connect to SQL Server. This error is simply reported as 18456, and the error text is "Login failed for user ‘username'" Well, you already had understood that you could not...
Page 1 of 1 (9 items)
MSDN Blogs
>
Common tips and tricks from a SQL Developer Support perspective
>
July, 2008