When creating a system DSN via the ODBC Admistrator dialog...
What is the differecne between "SQL Native Client" and "SQL Server" drivers
listed in the "Create New Data Source" drivers list?
How do they differ?
"Coder23" <Coder23@.discussions.microsoft.com> wrote in message
news:B50C82B2-70C8-4F28-89CA-248F039A048E@.microsoft.com...
> When creating a system DSN via the ODBC Admistrator dialog...
> What is the differecne between "SQL Native Client" and "SQL
> Server" drivers
> listed in the "Create New Data Source" drivers list?
> How do they differ?
From MSDN:
"SQL Native Client is a data access technology that is new to
Microsoft SQL Server 2005, and it is a stand-alone data access
application programming interface (API) that is used for both OLE
DB and ODBC. It combines the SQL OLE DB provider and the SQL ODBC
driver into one native dynamic-link library (DLL) while also
providing new functionality above and beyond that supplied by the
Microsoft Data Access Components (MDAC). SQL Native Client can be
used to create new applications or enhance existing applications
that need to take advantage of new SQL Server 2005 features such
as multiple active result sets (MARS), user-defined data types
(UDT), query notifications, snapshot isolation, and XML data type
support."
- Arnie
|||Thanks, that helps... but what about the other one listed? ("SQL Server"
driver)
Which is the appropriate one to use in an IIS/Website scenario in terms of
data access?
"Arnie" wrote:
> "Coder23" <Coder23@.discussions.microsoft.com> wrote in message
> news:B50C82B2-70C8-4F28-89CA-248F039A048E@.microsoft.com...
> From MSDN:
> "SQL Native Client is a data access technology that is new to
> Microsoft SQL Server 2005, and it is a stand-alone data access
> application programming interface (API) that is used for both OLE
> DB and ODBC. It combines the SQL OLE DB provider and the SQL ODBC
> driver into one native dynamic-link library (DLL) while also
> providing new functionality above and beyond that supplied by the
> Microsoft Data Access Components (MDAC). SQL Native Client can be
> used to create new applications or enhance existing applications
> that need to take advantage of new SQL Server 2005 features such
> as multiple active result sets (MARS), user-defined data types
> (UDT), query notifications, snapshot isolation, and XML data type
> support."
> - Arnie
>
>
|||"Coder23" <Coder23@.discussions.microsoft.com> wrote in message
news:A3AAA0F0-1898-4453-8D19-9613BA7FAA08@.microsoft.com...
> Thanks, that helps... but what about the other one listed?
> ("SQL Server"
> driver)
> Which is the appropriate one to use in an IIS/Website scenario
> in terms of
> data access?
>
The 'normal' SQL Server Driver should be fine unless you plan to
use some of the new features that were mentioned for SQL Server
2005. We use SQL Server 2000. I haven't tried to run the new
driver against it yet.
- Arnie
Showing posts with label client. Show all posts
Showing posts with label client. Show all posts
Sunday, March 11, 2012
"SQL Native Client" / "SQL Server" drivers
When creating a system DSN via the ODBC Admistrator dialog...
What is the differecne between "SQL Native Client" and "SQL Server" drivers
listed in the "Create New Data Source" drivers list?
How do they differ?"Coder23" <Coder23@.discussions.microsoft.com> wrote in message
news:B50C82B2-70C8-4F28-89CA-248F039A048E@.microsoft.com...
> When creating a system DSN via the ODBC Admistrator dialog...
> What is the differecne between "SQL Native Client" and "SQL
> Server" drivers
> listed in the "Create New Data Source" drivers list?
> How do they differ?
From MSDN:
"SQL Native Client is a data access technology that is new to
Microsoft SQL Server 2005, and it is a stand-alone data access
application programming interface (API) that is used for both OLE
DB and ODBC. It combines the SQL OLE DB provider and the SQL ODBC
driver into one native dynamic-link library (DLL) while also
providing new functionality above and beyond that supplied by the
Microsoft Data Access Components (MDAC). SQL Native Client can be
used to create new applications or enhance existing applications
that need to take advantage of new SQL Server 2005 features such
as multiple active result sets (MARS), user-defined data types
(UDT), query notifications, snapshot isolation, and XML data type
support."
- Arnie|||Thanks, that helps... but what about the other one listed? ("SQL Server"
driver)
Which is the appropriate one to use in an IIS/Website scenario in terms of
data access?
"Arnie" wrote:
> "Coder23" <Coder23@.discussions.microsoft.com> wrote in message
> news:B50C82B2-70C8-4F28-89CA-248F039A048E@.microsoft.com...
> From MSDN:
> "SQL Native Client is a data access technology that is new to
> Microsoft SQL Server 2005, and it is a stand-alone data access
> application programming interface (API) that is used for both OLE
> DB and ODBC. It combines the SQL OLE DB provider and the SQL ODBC
> driver into one native dynamic-link library (DLL) while also
> providing new functionality above and beyond that supplied by the
> Microsoft Data Access Components (MDAC). SQL Native Client can be
> used to create new applications or enhance existing applications
> that need to take advantage of new SQL Server 2005 features such
> as multiple active result sets (MARS), user-defined data types
> (UDT), query notifications, snapshot isolation, and XML data type
> support."
> - Arnie
>
>|||"Coder23" <Coder23@.discussions.microsoft.com> wrote in message
news:A3AAA0F0-1898-4453-8D19-9613BA7FAA08@.microsoft.com...
> Thanks, that helps... but what about the other one listed?
> ("SQL Server"
> driver)
> Which is the appropriate one to use in an IIS/Website scenario
> in terms of
> data access?
>
The 'normal' SQL Server Driver should be fine unless you plan to
use some of the new features that were mentioned for SQL Server
2005. We use SQL Server 2000. I haven't tried to run the new
driver against it yet.
- Arnie
What is the differecne between "SQL Native Client" and "SQL Server" drivers
listed in the "Create New Data Source" drivers list?
How do they differ?"Coder23" <Coder23@.discussions.microsoft.com> wrote in message
news:B50C82B2-70C8-4F28-89CA-248F039A048E@.microsoft.com...
> When creating a system DSN via the ODBC Admistrator dialog...
> What is the differecne between "SQL Native Client" and "SQL
> Server" drivers
> listed in the "Create New Data Source" drivers list?
> How do they differ?
From MSDN:
"SQL Native Client is a data access technology that is new to
Microsoft SQL Server 2005, and it is a stand-alone data access
application programming interface (API) that is used for both OLE
DB and ODBC. It combines the SQL OLE DB provider and the SQL ODBC
driver into one native dynamic-link library (DLL) while also
providing new functionality above and beyond that supplied by the
Microsoft Data Access Components (MDAC). SQL Native Client can be
used to create new applications or enhance existing applications
that need to take advantage of new SQL Server 2005 features such
as multiple active result sets (MARS), user-defined data types
(UDT), query notifications, snapshot isolation, and XML data type
support."
- Arnie|||Thanks, that helps... but what about the other one listed? ("SQL Server"
driver)
Which is the appropriate one to use in an IIS/Website scenario in terms of
data access?
"Arnie" wrote:
> "Coder23" <Coder23@.discussions.microsoft.com> wrote in message
> news:B50C82B2-70C8-4F28-89CA-248F039A048E@.microsoft.com...
> From MSDN:
> "SQL Native Client is a data access technology that is new to
> Microsoft SQL Server 2005, and it is a stand-alone data access
> application programming interface (API) that is used for both OLE
> DB and ODBC. It combines the SQL OLE DB provider and the SQL ODBC
> driver into one native dynamic-link library (DLL) while also
> providing new functionality above and beyond that supplied by the
> Microsoft Data Access Components (MDAC). SQL Native Client can be
> used to create new applications or enhance existing applications
> that need to take advantage of new SQL Server 2005 features such
> as multiple active result sets (MARS), user-defined data types
> (UDT), query notifications, snapshot isolation, and XML data type
> support."
> - Arnie
>
>|||"Coder23" <Coder23@.discussions.microsoft.com> wrote in message
news:A3AAA0F0-1898-4453-8D19-9613BA7FAA08@.microsoft.com...
> Thanks, that helps... but what about the other one listed?
> ("SQL Server"
> driver)
> Which is the appropriate one to use in an IIS/Website scenario
> in terms of
> data access?
>
The 'normal' SQL Server Driver should be fine unless you plan to
use some of the new features that were mentioned for SQL Server
2005. We use SQL Server 2000. I haven't tried to run the new
driver against it yet.
- Arnie
Tuesday, March 6, 2012
"Open Table Window" is read-only under SQL Query Analyzer
I have installed SQL Server 2000 with option "Client Tools Only"
I try to edit data using SQL Query Analyzer with Trusted Connection. I click on 'Open' of right-click on table objects. A "Open Table Window" is opened as read-only!!! "Add" and "Delete" are grey out!! I can't edit data.
I am trying to edit data using Server Explorer under Microsoft .NET with Trusted Connection. It works!!!
Help, Help!
Maybe the table does not have a Primary Key, check this first.
Dejan Sarka, SQL Server MVP
Associate Mentor
Solid Quality Learning
More than just Training
www.SolidQualityLearning.com
"Happy Programmer" <anonymous@.discussions.microsoft.com> wrote in message
news:9D59D138-BFAE-4CAB-A2C1-FF535B42F2C7@.microsoft.com...
> I have installed SQL Server 2000 with option "Client Tools Only"
> I try to edit data using SQL Query Analyzer with Trusted Connection. I
click on 'Open' of right-click on table objects. A "Open Table Window" is
opened as read-only!!! "Add" and "Delete" are grey out!! I can't edit
data.
> I am trying to edit data using Server Explorer under Microsoft .NET with
Trusted Connection. It works!!!
> Help, Help!
|||I believe that you will only be able to modify data from the Open Table
function in Query Analyzer if the table has a primary key or unique
constraint or a unique index.
Steve Kass
Drew University
Happy Programmer wrote:
>I have installed SQL Server 2000 with option "Client Tools Only"
>I try to edit data using SQL Query Analyzer with Trusted Connection. I click on 'Open' of right-click on table objects. A "Open Table Window" is opened as read-only!!! "Add" and "Delete" are grey out!! I can't edit data.
>I am trying to edit data using Server Explorer under Microsoft .NET with Trusted Connection. It works!!!
>Help, Help!
>
|||I've tried it. It is able to modify if the table has primary key or unique index.
But is able to edit data using Server Explorer under Microsoft .NET with Trusted Connection even it has not any key or index.
Anyway, thanks a lot~!
I try to edit data using SQL Query Analyzer with Trusted Connection. I click on 'Open' of right-click on table objects. A "Open Table Window" is opened as read-only!!! "Add" and "Delete" are grey out!! I can't edit data.
I am trying to edit data using Server Explorer under Microsoft .NET with Trusted Connection. It works!!!
Help, Help!
Maybe the table does not have a Primary Key, check this first.
Dejan Sarka, SQL Server MVP
Associate Mentor
Solid Quality Learning
More than just Training
www.SolidQualityLearning.com
"Happy Programmer" <anonymous@.discussions.microsoft.com> wrote in message
news:9D59D138-BFAE-4CAB-A2C1-FF535B42F2C7@.microsoft.com...
> I have installed SQL Server 2000 with option "Client Tools Only"
> I try to edit data using SQL Query Analyzer with Trusted Connection. I
click on 'Open' of right-click on table objects. A "Open Table Window" is
opened as read-only!!! "Add" and "Delete" are grey out!! I can't edit
data.
> I am trying to edit data using Server Explorer under Microsoft .NET with
Trusted Connection. It works!!!
> Help, Help!
|||I believe that you will only be able to modify data from the Open Table
function in Query Analyzer if the table has a primary key or unique
constraint or a unique index.
Steve Kass
Drew University
Happy Programmer wrote:
>I have installed SQL Server 2000 with option "Client Tools Only"
>I try to edit data using SQL Query Analyzer with Trusted Connection. I click on 'Open' of right-click on table objects. A "Open Table Window" is opened as read-only!!! "Add" and "Delete" are grey out!! I can't edit data.
>I am trying to edit data using Server Explorer under Microsoft .NET with Trusted Connection. It works!!!
>Help, Help!
>
|||I've tried it. It is able to modify if the table has primary key or unique index.
But is able to edit data using Server Explorer under Microsoft .NET with Trusted Connection even it has not any key or index.
Anyway, thanks a lot~!
Thursday, February 16, 2012
"Failed to open a rowset"
Help me... I have a report which I'm loading using the following code. When I deploy the application in a client's pc "Failed to open a rowset" is the error that appears. I am using an ODBC connection. Any help would be appreciated...
Dim cr As New crptCMR
Dim crtableLogoninfos As New TableLogOnInfos
Dim crtableLogoninfo As New TableLogOnInfo
Dim crConnectionInfo As New ConnectionInfo
Dim CrTables As Tables
Dim CrTable As Table
Dim TableCounter
Dim crReportDocument As New crptCMR
With crConnectionInfo
.ServerName = sname
.DatabaseName = dbname
.UserID = uid
.Password = pwd
End With
CrTables = crReportDocument.Database.Tables
For Each CrTable In CrTables
crtableLogoninfo = CrTable.LogOnInfo
crtableLogoninfo.ConnectionInfo = crConnectionInfo
CrTable.ApplyLogOnInfo(crtableLogoninfo)
Next
CRVcmr.ReportSource = crReportDocumentOpen the report and do verify database
Dim cr As New crptCMR
Dim crtableLogoninfos As New TableLogOnInfos
Dim crtableLogoninfo As New TableLogOnInfo
Dim crConnectionInfo As New ConnectionInfo
Dim CrTables As Tables
Dim CrTable As Table
Dim TableCounter
Dim crReportDocument As New crptCMR
With crConnectionInfo
.ServerName = sname
.DatabaseName = dbname
.UserID = uid
.Password = pwd
End With
CrTables = crReportDocument.Database.Tables
For Each CrTable In CrTables
crtableLogoninfo = CrTable.LogOnInfo
crtableLogoninfo.ConnectionInfo = crConnectionInfo
CrTable.ApplyLogOnInfo(crtableLogoninfo)
Next
CRVcmr.ReportSource = crReportDocumentOpen the report and do verify database
Thursday, February 9, 2012
"Changed Context to ..." message when editing permissions w/ VBA
I have a client using a small SQL Express database with an Access front end.
I've created a form in the front end that allows a supervisor the ability to perform two very basic security operations. 1) Adding a new user, and 2) granting/removing write privileges. The code behind the form uses VBA to build some T-SQL strings and then executes them via an ADO connection.
The strings are as follows:
1) Add new login to server:
"CREATE LOGIN [NETWORK\UserName] FROM WINDOWS WITH DEFAULT_DATABASE = MyDatabase"
2) Add user to database:
"USE MyDatabase CREATE USER [NETWORK\UserName]"
3) Grant Write Permissions:
" USE MyDatabase EXEC sp_addrolemember 'db_datawriter', 'NETWORK\UserName' "
4) Remove Write Permissions:
" USE MyDatabase EXEC sp_droprolemember 'db_datawriter', 'NETWORK\UserName' "
I have full privileges over the server & database, and everything runs perfectly.
However, when the supervisor - whose login includes security admin privileges - tries this, he gets a message that says "Changed Context to MyDatabase, Error# -2147217900, 80040e14" and the code fails.
If I grant him "db_owner" status, the message does not come up and everything runs perfectly.
I'm not a security guru or anything, but I suspect that it's not the greatest idea to hand out db_owner privileges.
I ran a search, and the best I could come up with were a couple of KB articles:
http://support.microsoft.com/default.aspx?scid=KB;EN-US;197459
http://support.microsoft.com/default.aspx?scid=KB;EN-US;143339
I'm not even sure these articles are talking about what's happening..
Any ideas?When is the last time your boss ran an office update? Or more specifically, which MDAC is he using?|||When is the last time your boss ran an office update? Or more specifically, which MDAC is he using?
I'm not at the client's location right now, so I can't give a firm answer.. but I had someone there gather the following info..
Access is version 11.6566.8132 SP2
They're running XP Pro version 2002 SP2.
Per this page: http://support.microsoft.com/kb/231943/en-us they should be on at least MDAC 2.8 SP1. However based on the release dates shown on that page, I wouldn't be suprised if they were running 2.8 SP2.
Does that help?|||Ok, went by their office yesterday. MDAC is version 2.8.1117.0.
After a little more time spent, it appears as if this is the 'informational' message passed back to ODBC. It appears that I need to figure out how to trap for it in VB. The KB articles I posted got me started, but I need some more work..
I also seem to still have a SQL issue.. In the little bit of troubleshooting I had time for, it also appears that I have a 2nd error coming in behind the "changed context.." message. If the user is not a dbowner, it says that he doesn't have permissions to run these operations.
Is this correct? Is dbowner status required to change permissions of other users?
I've created a form in the front end that allows a supervisor the ability to perform two very basic security operations. 1) Adding a new user, and 2) granting/removing write privileges. The code behind the form uses VBA to build some T-SQL strings and then executes them via an ADO connection.
The strings are as follows:
1) Add new login to server:
"CREATE LOGIN [NETWORK\UserName] FROM WINDOWS WITH DEFAULT_DATABASE = MyDatabase"
2) Add user to database:
"USE MyDatabase CREATE USER [NETWORK\UserName]"
3) Grant Write Permissions:
" USE MyDatabase EXEC sp_addrolemember 'db_datawriter', 'NETWORK\UserName' "
4) Remove Write Permissions:
" USE MyDatabase EXEC sp_droprolemember 'db_datawriter', 'NETWORK\UserName' "
I have full privileges over the server & database, and everything runs perfectly.
However, when the supervisor - whose login includes security admin privileges - tries this, he gets a message that says "Changed Context to MyDatabase, Error# -2147217900, 80040e14" and the code fails.
If I grant him "db_owner" status, the message does not come up and everything runs perfectly.
I'm not a security guru or anything, but I suspect that it's not the greatest idea to hand out db_owner privileges.
I ran a search, and the best I could come up with were a couple of KB articles:
http://support.microsoft.com/default.aspx?scid=KB;EN-US;197459
http://support.microsoft.com/default.aspx?scid=KB;EN-US;143339
I'm not even sure these articles are talking about what's happening..
Any ideas?When is the last time your boss ran an office update? Or more specifically, which MDAC is he using?|||When is the last time your boss ran an office update? Or more specifically, which MDAC is he using?
I'm not at the client's location right now, so I can't give a firm answer.. but I had someone there gather the following info..
Access is version 11.6566.8132 SP2
They're running XP Pro version 2002 SP2.
Per this page: http://support.microsoft.com/kb/231943/en-us they should be on at least MDAC 2.8 SP1. However based on the release dates shown on that page, I wouldn't be suprised if they were running 2.8 SP2.
Does that help?|||Ok, went by their office yesterday. MDAC is version 2.8.1117.0.
After a little more time spent, it appears as if this is the 'informational' message passed back to ODBC. It appears that I need to figure out how to trap for it in VB. The KB articles I posted got me started, but I need some more work..
I also seem to still have a SQL issue.. In the little bit of troubleshooting I had time for, it also appears that I have a 2nd error coming in behind the "changed context.." message. If the user is not a dbowner, it says that he doesn't have permissions to run these operations.
Is this correct? Is dbowner status required to change permissions of other users?
"Cannot recover the master database. Exiting." and beyond
I have a client who gets "Cannot recover the master database.
Exiting." when trying to start the MSDE.
As it happens I must come up with an answer to why this may happen.
I searched this group and beyond and though the cure looks to be
"rebuild and reinstall" I need you gurus out there to, tell me why
this may happen.
Please help,
JohnHi,
First try to start SQL Serevr in Minimal config. mode, if fails,
Do you have the Backup for Master database?
If yes then,
1. Rebuild the master
2. STart SQL server in single user mode
3. Apply the master backup to master database
4. Restart SQL server
Thanks
Hari
MCDBA
"john" <abcmyemail@.yahoo.com> wrote in message
news:35644fe1.0312121140.1a4ab125@.posting.google.com...
> I have a client who gets "Cannot recover the master database.
> Exiting." when trying to start the MSDE.
> As it happens I must come up with an answer to why this may happen.
> I searched this group and beyond and though the cure looks to be
> "rebuild and reinstall" I need you gurus out there to, tell me why
> this may happen.
>
> Please help,
> John
Exiting." when trying to start the MSDE.
As it happens I must come up with an answer to why this may happen.
I searched this group and beyond and though the cure looks to be
"rebuild and reinstall" I need you gurus out there to, tell me why
this may happen.
Please help,
JohnHi,
First try to start SQL Serevr in Minimal config. mode, if fails,
Do you have the Backup for Master database?
If yes then,
1. Rebuild the master
2. STart SQL server in single user mode
3. Apply the master backup to master database
4. Restart SQL server
Thanks
Hari
MCDBA
"john" <abcmyemail@.yahoo.com> wrote in message
news:35644fe1.0312121140.1a4ab125@.posting.google.com...
> I have a client who gets "Cannot recover the master database.
> Exiting." when trying to start the MSDE.
> As it happens I must come up with an answer to why this may happen.
> I searched this group and beyond and though the cure looks to be
> "rebuild and reinstall" I need you gurus out there to, tell me why
> this may happen.
>
> Please help,
> John
Subscribe to:
Posts (Atom)
