old sql2k5 folder: dear

Showing posts with label dear. Show all posts

Friday, March 30, 2012

One favour plz.

Dear Professional...
Can you plz tell me one thing like I have one XML file which is already
saved in C:\File1.xml path.
I want to parse that File1.xml file and save it into database through any
stored procedure or any command but the problem is that how can I call the
file File1.xml from the hard disk and parse it and save it into customer
table. I would highly appreciate if any one guide me this.
Thanks
NOOR
You may want to check out www.sqlxml.org
It has several short tips and guidelines on using the xml features with SQL
Server 2000. In your case, OPENXML function would be appropriate, the
details & examples of which can be found in SQL Server Books Online.
Anith

Monday, March 26, 2012

Once replicated DB can't be detached

Dear Sir,
I have a database which has been "Transactional" replicated one table. I
already deleted the subscription and deleted the publication. But still the
database has the replicate icon besides on EM and not allowing me to detach.
What can I do to refresh the DB status in order to allow me to detach the db?
Many thanks!
Henry
Try this:
EXEC sp_dboption 'DBNameHere', 'published', 'false'
GO
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Henry" <Henry@.discussions.microsoft.com> wrote in message
news:9DB717B5-CCE8-41B8-A7CC-15E422F750E1@.microsoft.com...
Dear Sir,
I have a database which has been "Transactional" replicated one table. I
already deleted the subscription and deleted the publication. But still the
database has the replicate icon besides on EM and not allowing me to detach.
What can I do to refresh the DB status in order to allow me to detach the
db?
Many thanks!
Henry
|||Thanks!
"Narayana Vyas Kondreddi" wrote:

> Try this:
> EXEC sp_dboption 'DBNameHere', 'published', 'false'
> GO
> --
> HTH,
> Vyas, MVP (SQL Server)
> SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
>
> "Henry" <Henry@.discussions.microsoft.com> wrote in message
> news:9DB717B5-CCE8-41B8-A7CC-15E422F750E1@.microsoft.com...
> Dear Sir,
> I have a database which has been "Transactional" replicated one table. I
> already deleted the subscription and deleted the publication. But still the
> database has the replicate icon besides on EM and not allowing me to detach.
> What can I do to refresh the DB status in order to allow me to detach the
> db?
> Many thanks!
> Henry
>
>

Once replicated DB can't be detached

Dear Sir,
I have a database which has been "Transactional" replicated one table. I
already deleted the subscription and deleted the publication. But still the
database has the replicate icon besides on EM and not allowing me to detach.
What can I do to refresh the DB status in order to allow me to detach the db
?
Many thanks!
HenryTry this:
EXEC sp_dboption 'DBNameHere', 'published', 'false'
GO
--
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Henry" <Henry@.discussions.microsoft.com> wrote in message
news:9DB717B5-CCE8-41B8-A7CC-15E422F750E1@.microsoft.com...
Dear Sir,
I have a database which has been "Transactional" replicated one table. I
already deleted the subscription and deleted the publication. But still the
database has the replicate icon besides on EM and not allowing me to detach.
What can I do to refresh the DB status in order to allow me to detach the
db?
Many thanks!
Henry|||Thanks!
"Narayana Vyas Kondreddi" wrote:

> Try this:
> EXEC sp_dboption 'DBNameHere', 'published', 'false'
> GO
> --
> HTH,
> Vyas, MVP (SQL Server)
> SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
>
> "Henry" <Henry@.discussions.microsoft.com> wrote in message
> news:9DB717B5-CCE8-41B8-A7CC-15E422F750E1@.microsoft.com...
> Dear Sir,
> I have a database which has been "Transactional" replicated one table. I
> already deleted the subscription and deleted the publication. But still th
e
> database has the replicate icon besides on EM and not allowing me to detac
h.
> What can I do to refresh the DB status in order to allow me to detach the
> db?
> Many thanks!
> Henry
>
>sql

Once replicated DB can't be detached

Dear Sir,
I have a database which has been "Transactional" replicated one table. I
already deleted the subscription and deleted the publication. But still the
database has the replicate icon besides on EM and not allowing me to detach.
What can I do to refresh the DB status in order to allow me to detach the db?
Many thanks!
HenryTry this:
EXEC sp_dboption 'DBNameHere', 'published', 'false'
GO
--
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Henry" <Henry@.discussions.microsoft.com> wrote in message
news:9DB717B5-CCE8-41B8-A7CC-15E422F750E1@.microsoft.com...
Dear Sir,
I have a database which has been "Transactional" replicated one table. I
already deleted the subscription and deleted the publication. But still the
database has the replicate icon besides on EM and not allowing me to detach.
What can I do to refresh the DB status in order to allow me to detach the
db?
Many thanks!
Henry|||Thanks!
"Narayana Vyas Kondreddi" wrote:
> Try this:
> EXEC sp_dboption 'DBNameHere', 'published', 'false'
> GO
> --
> HTH,
> Vyas, MVP (SQL Server)
> SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
>
> "Henry" <Henry@.discussions.microsoft.com> wrote in message
> news:9DB717B5-CCE8-41B8-A7CC-15E422F750E1@.microsoft.com...
> Dear Sir,
> I have a database which has been "Transactional" replicated one table. I
> already deleted the subscription and deleted the publication. But still the
> database has the replicate icon besides on EM and not allowing me to detach.
> What can I do to refresh the DB status in order to allow me to detach the
> db?
> Many thanks!
> Henry
>
>

Friday, March 23, 2012

OLTP vs Reporting Database vs OLAP Database

Dear All,
I have a fundamental questions regarding my design of my SQL Server
Database.
Current SQL Server 2000 Design Setting (in one server)
-1 Database for OLTP
-1 Database for OLAP -> Generating Cubes
Planned SQL Server 2000 Design Setting (in two servers):
-1 Database for OLTP -> at Server A
-1 Database for Reporting Purposes -> at Server B
-1 Database for OLAP -> at Server B
My Question -> Is it necessary to separate reporting database and OLAP
database?
Any sugestion please.
Thanks
Robert Lie
if you want to provide reports based on a copy of your OLTP database, so you
can create a "read-only" database optimized for reporting purpose.
you can provide (near)real time reports.
this usage as an advantage: you don't impat you operationnal server by
executing complex queries. but.. garbage in garbage out...
if you want to have a common and cleansed database for both reporting and
analysis to insure that you'll allways display the same information, use the
same database for RS + OLAP. but, generally, this database in not real-time
updated.
so what is your primary usage for your reports?
- operationnal purpose
- analytical purpose
but you can also provide reports based on the 2 databases regarding the
performance of your queries.
if you have some performance problems with your OLTP database (the copy on
the server B) then the OLAP database and cubes will improove the response
time.
also, look at the number of users... 100 users on a 10seconds report vs 100
users on a 1second report...
"Robert Lie" <robert.lie24@.gmail.com> wrote in message
news:uD8T74gSFHA.2520@.TK2MSFTNGP09.phx.gbl...
> Dear All,
> I have a fundamental questions regarding my design of my SQL Server
> Database.
> Current SQL Server 2000 Design Setting (in one server)
> -1 Database for OLTP
> -1 Database for OLAP -> Generating Cubes
> Planned SQL Server 2000 Design Setting (in two servers):
> -1 Database for OLTP -> at Server A
> -1 Database for Reporting Purposes -> at Server B
> -1 Database for OLAP -> at Server B
> My Question -> Is it necessary to separate reporting database and OLAP
> database?
> Any sugestion please.
> Thanks
> Robert Lie
|||Here my considerations
1. Reporting Database:
- To provide operational reports with 10 minutes delay.
- Not Disturbing OLTP Server
- Incrase response time for users who access reports (estimation
max 20 users in the same time)
2. OLAP Database:
- To generate Cubes
- To boost the Cubes generation performance since it won't
affected by users who access reports.
- For analytical purpose
And both of them are not real-time.
Please explain further about garbage in garbage out?
So what do you think of my considerations?
Thanks a lot
Robert Lie
Jj wrote:
> if you want to provide reports based on a copy of your OLTP database, so you
> can create a "read-only" database optimized for reporting purpose.
> you can provide (near)real time reports.
> this usage as an advantage: you don't impat you operationnal server by
> executing complex queries. but.. garbage in garbage out...
> if you want to have a common and cleansed database for both reporting and
> analysis to insure that you'll allways display the same information, use the
> same database for RS + OLAP. but, generally, this database in not real-time
> updated.
> so what is your primary usage for your reports?
> - operationnal purpose
> - analytical purpose
> but you can also provide reports based on the 2 databases regarding the
> performance of your queries.
> if you have some performance problems with your OLTP database (the copy on
> the server B) then the OLAP database and cubes will improove the response
> time.
> also, look at the number of users... 100 users on a 10seconds report vs 100
> users on a 1second report...
>
> "Robert Lie" <robert.lie24@.gmail.com> wrote in message
> news:uD8T74gSFHA.2520@.TK2MSFTNGP09.phx.gbl...
>
>
|||creating a copy of the OLTP database is good choice
you can use the log shipping function to do this (or other methods)
(how do you plan to synchronize your databases?)
generating cubes will not lock your database if you do incremental updates
on a optimized cube. (or just a litlle lock)
Partitions will help you for the cube process step.
But your design appear to be good.
garbage in garbage out = bad data quality in the source = bad quality in
output (non existant clientID, duplicated product name, duplicated
records...). so an ETL tool can improove the data quality during the
process. or if you want to synchronize multiple sources (like reference
tables and operationnal tables)
But these steps reduce the loading time by adding data cleansing time.
if you think next step (which is SQL 2005) you'll have a lot of new features
to help you.
for example, you will be able to load directly a partition of your cube
while you'll load your database, so 1 read and 2 destinations
(and there is a lot of options)
"Robert Lie" <robert.lie24@.gmail.com> wrote in message
news:%23RX3SehSFHA.248@.TK2MSFTNGP15.phx.gbl...[vbcol=seagreen]
> Here my considerations
> 1. Reporting Database:
> - To provide operational reports with 10 minutes delay.
> - Not Disturbing OLTP Server
> - Incrase response time for users who access reports (estimation
> max 20 users in the same time)
> 2. OLAP Database:
> - To generate Cubes
> - To boost the Cubes generation performance since it won't affected by
> users who access reports.
> - For analytical purpose
> And both of them are not real-time.
> Please explain further about garbage in garbage out?
> So what do you think of my considerations?
> Thanks a lot
> Robert Lie
>
> Jj wrote:
|||Actually what I want to do is not just copy the OLTP Database, but DTS
from OLTP tables to summaries form Tables to eliminate the join and
complex calculation when show up some reports.
-> What do you think?
Since my SQL Server 2000 is standard edition so I can't do a kind of
cube partition.
Thanks
Jj wrote:
> creating a copy of the OLTP database is good choice
> you can use the log shipping function to do this (or other methods)
> (how do you plan to synchronize your databases?)
> generating cubes will not lock your database if you do incremental updates
> on a optimized cube. (or just a litlle lock)
> Partitions will help you for the cube process step.
> But your design appear to be good.
> garbage in garbage out = bad data quality in the source = bad quality in
> output (non existant clientID, duplicated product name, duplicated
> records...). so an ETL tool can improove the data quality during the
> process. or if you want to synchronize multiple sources (like reference
> tables and operationnal tables)
> But these steps reduce the loading time by adding data cleansing time.
> if you think next step (which is SQL 2005) you'll have a lot of new features
> to help you.
> for example, you will be able to load directly a partition of your cube
> while you'll load your database, so 1 read and 2 destinations
> (and there is a lot of options)
> "Robert Lie" <robert.lie24@.gmail.com> wrote in message
> news:%23RX3SehSFHA.248@.TK2MSFTNGP15.phx.gbl...
>
sql

OLTP vs Reporting Database vs OLAP Database

Dear All,
I have a fundamental questions regarding my design of my SQL Server
Database.
Current SQL Server 2000 Design Setting (in one server)
-1 Database for OLTP
-1 Database for OLAP -> Generating Cubes
Planned SQL Server 2000 Design Setting (in two servers):
-1 Database for OLTP -> at Server A
-1 Database for Reporting Purposes -> at Server B
-1 Database for OLAP -> at Server B
My Question -> Is it necessary to separate reporting database and OLAP
database?
Any sugestion please.
Thanks
Robert Lieif you want to provide reports based on a copy of your OLTP database, so you
can create a "read-only" database optimized for reporting purpose.
you can provide (near)real time reports.
this usage as an advantage: you don't impat you operationnal server by
executing complex queries. but.. garbage in garbage out...
if you want to have a common and cleansed database for both reporting and
analysis to insure that you'll allways display the same information, use the
same database for RS + OLAP. but, generally, this database in not real-time
updated.
so what is your primary usage for your reports?
- operationnal purpose
- analytical purpose
but you can also provide reports based on the 2 databases regarding the
performance of your queries.
if you have some performance problems with your OLTP database (the copy on
the server B) then the OLAP database and cubes will improove the response
time.
also, look at the number of users... 100 users on a 10seconds report vs 100
users on a 1second report...
"Robert Lie" <robert.lie24@.gmail.com> wrote in message
news:uD8T74gSFHA.2520@.TK2MSFTNGP09.phx.gbl...
> Dear All,
> I have a fundamental questions regarding my design of my SQL Server
> Database.
> Current SQL Server 2000 Design Setting (in one server)
> -1 Database for OLTP
> -1 Database for OLAP -> Generating Cubes
> Planned SQL Server 2000 Design Setting (in two servers):
> -1 Database for OLTP -> at Server A
> -1 Database for Reporting Purposes -> at Server B
> -1 Database for OLAP -> at Server B
> My Question -> Is it necessary to separate reporting database and OLAP
> database?
> Any sugestion please.
> Thanks
> Robert Lie|||Here my considerations
1. Reporting Database:
- To provide operational reports with 10 minutes delay.
- Not Disturbing OLTP Server
- Incrase response time for users who access reports (estimation
max 20 users in the same time)
2. OLAP Database:
- To generate Cubes
- To boost the Cubes generation performance since it won't
affected by users who access reports.
- For analytical purpose
And both of them are not real-time.
Please explain further about garbage in garbage out?
So what do you think of my considerations?
Thanks a lot
Robert Lie
Jj wrote:
> if you want to provide reports based on a copy of your OLTP database, so y
ou
> can create a "read-only" database optimized for reporting purpose.
> you can provide (near)real time reports.
> this usage as an advantage: you don't impat you operationnal server by
> executing complex queries. but.. garbage in garbage out...
> if you want to have a common and cleansed database for both reporting and
> analysis to insure that you'll allways display the same information, use t
he
> same database for RS + OLAP. but, generally, this database in not real-tim
e
> updated.
> so what is your primary usage for your reports?
> - operationnal purpose
> - analytical purpose
> but you can also provide reports based on the 2 databases regarding the
> performance of your queries.
> if you have some performance problems with your OLTP database (the copy on
> the server B) then the OLAP database and cubes will improove the response
> time.
> also, look at the number of users... 100 users on a 10seconds report vs 10
0
> users on a 1second report...
>
> "Robert Lie" <robert.lie24@.gmail.com> wrote in message
> news:uD8T74gSFHA.2520@.TK2MSFTNGP09.phx.gbl...
>
>
>|||creating a copy of the OLTP database is good choice
you can use the log shipping function to do this (or other methods)
(how do you plan to synchronize your databases?)
generating cubes will not lock your database if you do incremental updates
on a optimized cube. (or just a litlle lock)
Partitions will help you for the cube process step.
But your design appear to be good.
garbage in garbage out = bad data quality in the source = bad quality in
output (non existant clientID, duplicated product name, duplicated
records...). so an ETL tool can improove the data quality during the
process. or if you want to synchronize multiple sources (like reference
tables and operationnal tables)
But these steps reduce the loading time by adding data cleansing time.
if you think next step (which is SQL 2005) you'll have a lot of new features
to help you.
for example, you will be able to load directly a partition of your cube
while you'll load your database, so 1 read and 2 destinations
(and there is a lot of options)
"Robert Lie" <robert.lie24@.gmail.com> wrote in message
news:%23RX3SehSFHA.248@.TK2MSFTNGP15.phx.gbl...[vbcol=seagreen]
> Here my considerations
> 1. Reporting Database:
> - To provide operational reports with 10 minutes delay.
> - Not Disturbing OLTP Server
> - Incrase response time for users who access reports (estimation
> max 20 users in the same time)
> 2. OLAP Database:
> - To generate Cubes
> - To boost the Cubes generation performance since it won't affected by
> users who access reports.
> - For analytical purpose
> And both of them are not real-time.
> Please explain further about garbage in garbage out?
> So what do you think of my considerations?
> Thanks a lot
> Robert Lie
>
> Jj wrote:|||Actually what I want to do is not just copy the OLTP Database, but DTS
from OLTP tables to summaries form Tables to eliminate the join and
complex calculation when show up some reports.
-> What do you think?
Since my SQL Server 2000 is standard edition so I can't do a kind of
cube partition.
Thanks
Jj wrote:
> creating a copy of the OLTP database is good choice
> you can use the log shipping function to do this (or other methods)
> (how do you plan to synchronize your databases?)
> generating cubes will not lock your database if you do incremental updates
> on a optimized cube. (or just a litlle lock)
> Partitions will help you for the cube process step.
> But your design appear to be good.
> garbage in garbage out = bad data quality in the source = bad quality in
> output (non existant clientID, duplicated product name, duplicated
> records...). so an ETL tool can improove the data quality during the
> process. or if you want to synchronize multiple sources (like reference
> tables and operationnal tables)
> But these steps reduce the loading time by adding data cleansing time.
> if you think next step (which is SQL 2005) you'll have a lot of new featur
es
> to help you.
> for example, you will be able to load directly a partition of your cube
> while you'll load your database, so 1 read and 2 destinations
> (and there is a lot of options)
> "Robert Lie" <robert.lie24@.gmail.com> wrote in message
> news:%23RX3SehSFHA.248@.TK2MSFTNGP15.phx.gbl...
>
>

Friday, March 9, 2012

OLE DB provider MSDAORA was unable to begin a distributed transaction

Dear all,

I have been attempting to set up a linked server in SQL Server 2000 to point to an Oracle database (a very old Oracle database, v7!).

The linked server set up works fine. Then I created a database on the same SQL Server. Within that database I created a view which reads information from a view in the Oracle database (linked server). When I attempted to create this view in Enterprise Manager, I get the following error:

"The operation could not be performed because the OLE DB provider 'MSDAORA' was unable to begin a distributed transaction."

And so I created the view in Query Analyzer. This worked perfectly, no errors, and I can now go into Enterprise Manager and call up the view, which happily goes off to the view in the Oracle linked server and pulls back the info. BUT, when I attempt to do the same thing through an application on a different machine (using OLE Db, and a UDL to connect) the same error as above appears.

Does anyone know what this error means, and where I went wrong? Any help greatly appreciated. My view onto the linked server looks like this:

"CREATE VIEW dbo.NLPG_VIEW
AS
SELECT * from openquery(sadaslink, 'select * from NLPG_VIEW')"

Many thanks in advance for your wisdom!

P.S I wondered whether I need to check if the distributed transaction co-ordinator is running but don't know how.
Thanks,http://www.aspfaq.com/2455 fyi.|||Thanks, I've already had aread through this. I did create the view in query analyzer but the problem now is that I can't get it to work from a remote application. I think I need to look into the distributed transaction co-ordinator, but I don't know how or where. How do I see if it is running? How do I get it running?|||On the SQL Server, start the SQL Services Manager. Change the Service to Distributed Transaction Coordinator. Play to your heart's content!

FYI, with Oracle 7.3 I needed to use SET REMOTE_PROC_TRANSACTIONS (http://msdn.microsoft.com/library/en-us/tsqlref/ts_set-set_206r.asp) to make things happy.

-PatP|||Would SET_REMOTE_PROC_TRANSACTIONS have to be coded into the app, as I can't put it in the SQL in the view can I?|||http://www.microsoft.com/technet/prodtechnol/sql/2000/books/c08ppcsq.mspx a guide to the solution.
Also check whether compatible Oracle driver is being used to connect, try with latest drivers.|||When you said remote procedure transactions, is that the same as setting remote procedure call in the GUI in enterprise manager? RPC and RPC OUT?

Thanks,
Paula|||No Polly, the concepts are related, but definitely not the same.

The problem is that SQL Server uses many flavors of locks in order to acheive true data consistancy... Some locks prohibit writing, some prohibit any access at all, and some do things that are difficult to describe in English, but make the engine behave as well as possible.

I haven't tried this in a long time, and no longer have an Oracle 7.x server to even test with, but I think you could get by with:SET REMOTE_PROC_TRANSACTIONS OFF
GO
CREATE VIEW dbo.NLPG_VIEW
AS
SELECT * from openquery(sadaslink, 'select * from NLPG_VIEW')All I can suggest that you do is to try it... I don't see how the attempt could hurt anything.

-PatP|||Thanks very much, I'll try it. Can't test it until next week, but Il'l let you know the results.

Wednesday, March 7, 2012

Ole DB Example For Windows Mobile 5.0

Dear All:

Is there a tutorial for WM5.0 to connect to SQL CE 3.0 using Ole DB using the headers:

#include "ca_merge30.h"

#include "ssceoledb30.h"

#include "ssceerr30.h"

The example Northwind at "Sql Mobile 5.0" doesn't works with WM5.0 SDK, due to imcompatibility issues. It works with the WM2003 sdk, but i'm programming in native c++ for WM5 devices.

I'm using the header from SQL Everywhere.

Thanks.

Alfredo Mendiola Loyola

Lima Perú

Please look at the KB articles

http://support.microsoft.com/default.aspx?scid=kb;en-us;914174&sd=rss&spid=2852

and the following post on this forum

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=313150&SiteID=1

Thanks

Arun

Monday, February 20, 2012

Old Sql Server

Dear folks,
I can’t work out with that. I’m trying to add into my Enterprise Manager
(Sql2k) a sql Server 6.5 but appears this error:
Sql Server Registration failed because of the connection failure displayed
below: Do you wish to Register anyway?
[SQL- DMO] Sql Server SRVSMS2 must be upgraded to version 7.0 or later to be
administered by this version of sql-dmo
Any thought/solution in order to avoid upgrade that SQL to 7.0? I’ve been
tried it from Sql Server 7.0 and I obtain the same result.
Thanks in advance and regards,No. EM 7.0 can only connect to 7.0. EM 2000 can only connect to 2000 and 7.0
. None of those EM can
connect to 6.5.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Enric" <Enric@.discussions.microsoft.com> wrote in message
news:F7ABFAB7-81BB-49C0-9ECC-50585C4B048B@.microsoft.com...
> Dear folks,
> I can't work out with that. I'm trying to add into my Enterprise Manager
> (Sql2k) a sql Server 6.5 but appears this error:
> Sql Server Registration failed because of the connection failure displayed
> below: Do you wish to Register anyway?
> [SQL- DMO] Sql Server SRVSMS2 must be upgraded to version 7.0 or later to
be
> administered by this version of sql-dmo
> Any thought/solution in order to avoid upgrade that SQL to 7.0? I've been
> tried it from Sql Server 7.0 and I obtain the same result.
> Thanks in advance and regards,
>|||you are talking about I use ODBC or import data from Sql Server 6.5 to Acces
s
and from there to the recent versions?
Thanks for your input
"Tibor Karaszi" wrote:

> No. EM 7.0 can only connect to 7.0. EM 2000 can only connect to 2000 and 7
.0. None of those EM can
> connect to 6.5.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Enric" <Enric@.discussions.microsoft.com> wrote in message
> news:F7ABFAB7-81BB-49C0-9ECC-50585C4B048B@.microsoft.com...
>
>|||I'm sorry but I don't understand your question. I simply replied saying that
the Enterprise Manager
that comes with 7.0 or 2000 cannot connect to a 6.5 server.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Enric" <Enric@.discussions.microsoft.com> wrote in message
news:B1D2C92D-7479-41B0-B07A-073A78D01DBB@.microsoft.com...
> you are talking about I use ODBC or import data from Sql Server 6.5 to Acc
ess
> and from there to the recent versions?
> Thanks for your input
> "Tibor Karaszi" wrote:
>|||don't worry it's my fault. I've formulated a new question
"Tibor Karaszi" wrote:

> I'm sorry but I don't understand your question. I simply replied saying th
at the Enterprise Manager
> that comes with 7.0 or 2000 cannot connect to a 6.5 server.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Enric" <Enric@.discussions.microsoft.com> wrote in message
> news:B1D2C92D-7479-41B0-B07A-073A78D01DBB@.microsoft.com...
>
>

Friday, March 30, 2012

One favour plz.

Monday, March 26, 2012

Once replicated DB can't be detached

Once replicated DB can't be detached

Once replicated DB can't be detached

Friday, March 23, 2012

OLTP vs Reporting Database vs OLAP Database

OLTP vs Reporting Database vs OLAP Database

OLTP vs Reporting Database vs OLAP Database

OLTP vs Reporting Database vs OLAP Database

OLTP vs Reporting Database vs OLAP Database

Friday, March 9, 2012

OLE DB provider MSDAORA was unable to begin a distributed transaction

Wednesday, March 7, 2012

Ole DB Example For Windows Mobile 5.0

Monday, February 20, 2012

Old Sql Server

old sql2k5 folder

Blog Archive

About Me