odbc driver?

Hello,
It has been over 5 years since I've had to use MS SQL.
I'm finding out the interface has changed and now I can't figure out how
to install the ODBC driver to a Server 2003 R2 box.
It's not where it used to be.
I've searched MS knowledge base but can't find anything.
Can someone please point me in the right direction.
thank you,
Sean
Are you sure it's not already there? It should be - MDAC is
part of the OS. I can't remember when they started calling
it MDAC but it was previously referred to as Universal Data
Access and you had the ODBC driver packs, etc. Now it's just
MDAC and MDAC is part of the OS so most MS drivers are
installed as part of the OS.
On the server from the start button, go to All Programs then
to Administrative Tools. From there select Data Sources
(ODBC) to bring up the ODBC Data Source Administrator
window. Click on the drivers tab and that will list the
drivers that are installed.
-Sue
On Mon, 09 Oct 2006 08:27:19 -0700, Sean <nomail@.here.com>
wrote:

>Hello,
>It has been over 5 years since I've had to use MS SQL.
>I'm finding out the interface has changed and now I can't figure out how
>to install the ODBC driver to a Server 2003 R2 box.
>It's not where it used to be.
>I've searched MS knowledge base but can't find anything.
>Can someone please point me in the right direction.
>thank you,
>Sean

ODBC datasource wont work on report server!!

Hi,

I have VS2005 and sql server express and ive created some reports using sql server
as a backend. everything works as it should.

THEN...

i created a report that uses a system DSN odbc source and it works in VS2005 it works fine.
i have deployed it to the report server and the datasource appears t be there, but when i try and run the report i ge the following message

An error has occurred during report processing.

An attempt has been made to use a data extension 'ODBC' that is not registered for this report server.anyone got any ideas how i can make this work? i have tried to find an explanation using google, but i cannot seem to see any thing that answers the question.

Regards,

Russ
Express versions of Reporting Services allow for data sources to only be local and must be a matching SKU of SQL Server.

ODBC connection to a seperate machine

I'm curious, can you set up a ODBC connection on one server, that points
to another computer on the network where the database is? I've tried
the computer name as //server2, but it doesn't seem to find it, yet, I
can get to it via the RDC within WinXP Pro.
Thanks,
Steve
"Steve Grosz" <boise_bound@.hotmail.com> wrote in message
news:eZknx$7UEHA.2520@.TK2MSFTNGP10.phx.gbl...
> I'm curious, can you set up a ODBC connection on one server, that points
> to another computer on the network where the database is? I've tried
> the computer name as //server2, but it doesn't seem to find it, yet, I
> can get to it via the RDC within WinXP Pro.
I do not believe that is allowed as which security credentials would be used
from the ODBC connection from server1 to server2? There are work-arounds,
for example you could use a linked server from SQL Server (say on server1)
and access the database on server2 from server1.
Steve

ODBC Connection Setup

I'm running SBS 2003 Premium SP1 and all is well. I've installed a new SQL
based application that requires a simple ODBC connection to the SQL database.
I have about 50 PCs to setup this ODBC link to my SBS server and there must
be a faster way to do this via a script or through Group Policies.
Has anyone tried this and how? I've used GPs for simple things like folder
redirection, but I'm not that strong on it.
Thanks.
Ken
I've taken to using file-based DSNs placed in a server folder that everyone
can access. It's turned out to be the best solution in my case.
Randall Arnold
"shepcon" <shepcon@.discussions.microsoft.com> wrote in message
news:E02D79DC-D435-4C36-9FF8-4C541F6116D4@.microsoft.com...
> I'm running SBS 2003 Premium SP1 and all is well. I've installed a new
> SQL
> based application that requires a simple ODBC connection to the SQL
> database.
> I have about 50 PCs to setup this ODBC link to my SBS server and there
> must
> be a faster way to do this via a script or through Group Policies.
> Has anyone tried this and how? I've used GPs for simple things like
> folder
> redirection, but I'm not that strong on it.
> Thanks.
> Ken
>

Occasional Authentication Failure

This is an interesting problem. I've never seen this in 5+ years of SQL Server work.
I just started a new job and the folks tell me this happens once a month or so.
We use Trusted Connections for the bulk of work. For some reason one of the multiple SQL Servers we run will just stop recognizing trusted connections. Out of the blue you will just start getting the "Cannot associate user (null) with a trusted connecti
on". The server will log an error indicating it can't find the Domain Controller. The strange thing is only 1 of our SQL Server boxes are affected. There are at least 3 other machines that don't have this issue.
Reboot the server and it's fixed. But, obviously we don't like bouncing production servers. These are running on Server 2003.
I was curious if anyone had seen this before.
Well usually when it says Null as the user , it is a problem with Windows
Authentication itself, not a SQL issue
Check this article :
How to troubleshoot connectivity issues in SQL Server 2000
http://support.microsoft.com/default...b;en-us;827422
HTH
Dylan
"Shawn Brock" <Shawn Brock@.discussions.microsoft.com> wrote in message
news:B62E0490-D630-4378-A3B9-FE36378221CE@.microsoft.com...
> This is an interesting problem. I've never seen this in 5+ years of SQL
Server work.
> I just started a new job and the folks tell me this happens once a month
or so.
> We use Trusted Connections for the bulk of work. For some reason one of
the multiple SQL Servers we run will just stop recognizing trusted
connections. Out of the blue you will just start getting the "Cannot
associate user (null) with a trusted connection". The server will log an
error indicating it can't find the Domain Controller. The strange thing is
only 1 of our SQL Server boxes are affected. There are at least 3 other
machines that don't have this issue.
> Reboot the server and it's fixed. But, obviously we don't like bouncing
production servers. These are running on Server 2003.
> I was curious if anyone had seen this before.

object_id function returns null

Hello,
I've been using object_id(object_name) function in some queries to retrieve
tables' ids without problems. However, those queries have started to fail
because object_id function returns null when the table name is like this one:
'MyPrefix.SampleTable'. I've checked sysobjects and the table exists there
and it has a valid id.
Any idea how to solve this? What are my options? Should I rewrite my queries
and use sysobject.name to perform JOINs?
I'm using SQL Server 2000.
Thanks in advance.
Is "MyPrefix" part of the table name or is it the owner of the table. If the former, you need to
quote it in OBJECT_ID, just the same way as when you refer to the table in a SELECT statement. But
the recommendation is to stick within the limits of standard identifiers when you name objects
(which among other thing doesn't allow a dot in the name):
CREATE TABLE "My.Table"(c1 int)
--Returns NULL, SQL Server assumes "My" is the owner
SELECT OBJECT_ID('My.Table')
--Returns the object id
SELECT OBJECT_ID('"My.Table"')
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Jos G" <JGeer@.nospamplease.onobox.com> wrote in message
news:75E956AC-BC7F-4A77-A149-3C0AD2B3E220@.microsoft.com...
> Hello,
> I've been using object_id(object_name) function in some queries to retrieve
> tables' ids without problems. However, those queries have started to fail
> because object_id function returns null when the table name is like this one:
> 'MyPrefix.SampleTable'. I've checked sysobjects and the table exists there
> and it has a valid id.
> Any idea how to solve this? What are my options? Should I rewrite my queries
> and use sysobject.name to perform JOINs?
> I'm using SQL Server 2000.
> Thanks in advance.
|||Thank you very much for you help. It works as you said.
I'm experiencing the issue in a customer's database.
Do you think it's safe to replace every call to object_id(table_name) with
object_id('"' + table_name + '"') or do you think I could face any collateral
effect?
Thanks again.
"Tibor Karaszi" wrote:

> Is "MyPrefix" part of the table name or is it the owner of the table. If the former, you need to
> quote it in OBJECT_ID, just the same way as when you refer to the table in a SELECT statement. But
> the recommendation is to stick within the limits of standard identifiers when you name objects
> (which among other thing doesn't allow a dot in the name):
> CREATE TABLE "My.Table"(c1 int)
> --Returns NULL, SQL Server assumes "My" is the owner
> SELECT OBJECT_ID('My.Table')
> --Returns the object id
> SELECT OBJECT_ID('"My.Table"')
>
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Jos G" <JGeer@.nospamplease.onobox.com> wrote in message
> news:75E956AC-BC7F-4A77-A149-3C0AD2B3E220@.microsoft.com...
>
|||> Do you think it's safe to replace every call to object_id(table_name) with
> object_id('"' + table_name + '"') or do you think I could face any collateral
> effect?
It depends. If the "object_name" part has the owner in it, you can't just quote the whole lot, you'd
have to quote each part:
CREATE TABLE "theTable"(c1 int)
--Returns object id
SELECT OBJECT_ID('"theTable"')
--Returns NULL
SELECT OBJECT_ID('"dbo.Table"')
--Should be
SELECT OBJECT_ID('"dbo"."Table"')
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Jos G" <JGeer@.nospamplease.onobox.com> wrote in message
news:6311228F-E9CD-4304-A3EE-292FAD6E6FFA@.microsoft.com...[vbcol=seagreen]
> Thank you very much for you help. It works as you said.
> I'm experiencing the issue in a customer's database.
> Do you think it's safe to replace every call to object_id(table_name) with
> object_id('"' + table_name + '"') or do you think I could face any collateral
> effect?
> Thanks again.
>
> "Tibor Karaszi" wrote: