Hi group,
[First time in, so feel free to shoot me if needed]
I am experienced with Postgresql, but relatively new to MSSQLServer.
I am building an application that uses MSSQL7.
Only basic stuff: 20 tables, foreign keys, a nice diagram, a few indexes.
No DTS, complex userstuff and that.
The target MSSQLServer will be 2000.
So now I need to know how to get my databaseschema and content from 7 to
2000.
As far as I can tell the option: GENERATE SQL only offers me an text-based
instruction for SCHEMA, not the content of table.
Right?
Question: Will MSSQL2000 understand the instructions created by MSSQL7?
As for the data itself:
The only way to export the data in the tables from MSSQL7 to MSSQL2000 I
found is by backing the whole thing up, as a binary.
(Using 'all tasks' --> 'Backup database')
Question: Will MSSQL2000 read and understand this file?
And will I need the databaseschema as generated by the GENERATE SQL option?
Or will MSSQL2000 be able to get that from the binary export?
Is this the way to do it, or am I missing lots of stuff?
Thanks for your time
Regards,
Erwin Moller
PS: I am sorry, but expect this is a very basic question. I just cannot find
any clear material on the subject online.
> I am building an application that uses MSSQL7.
> Only basic stuff: 20 tables, foreign keys, a nice diagram, a few indexes.
> No DTS, complex userstuff and that.
> The target MSSQLServer will be 2000.
> So now I need to know how to get my databaseschema and content from 7 to
> 2000.
> As far as I can tell the option: GENERATE SQL only offers me an text-based
> instruction for SCHEMA, not the content of table.
> Right?
Right.
> Question: Will MSSQL2000 understand the instructions created by MSSQL7?
Yes.
> As for the data itself:
> The only way to export the data in the tables from MSSQL7 to MSSQL2000 I
> found is by backing the whole thing up, as a binary.
> (Using 'all tasks' --> 'Backup database')
You found the easiest way. You could use Data transformation Services (DTS),
for example, as well.
> Question: Will MSSQL2000 read and understand this file?
Yes, simply restore the backup on SQL 2000 box. But I guess you will have to
change the physical path to data and log files, unless you have created the
database in 7.0 in your custom (not SQL default) folder and you have the
same directory structure in 2000.
> And will I need the databaseschema as generated by the GENERATE SQL
> option?
No.
> Or will MSSQL2000 be able to get that from the binary export?
Yes - backup has everything, schema and data.
> Is this the way to do it, or am I missing lots of stuff?
Yes, this is a good way. You have original 7.0 db, backup and new 2000 db
after the action. So. if anything goes wrong, you have 3 copies. And the
process is quite simple.
Dejan Sarka, SQL Server MVP
Mentor
www.SolidQualityLearning.com
|||Thanks Dejan Sarka!
I seldom receive such to-the-point answers. :-)
Regards,
Erwin Moller
Showing posts with label mssql2000. Show all posts
Showing posts with label mssql2000. Show all posts
Friday, March 9, 2012
MSSQL7 -> MSSQL2000 schema and data
Hi group,
[First time in, so feel free to shoot me if needed]
I am experienced with Postgresql, but relatively new to MSSQLServer.
I am building an application that uses MSSQL7.
Only basic stuff: 20 tables, foreign keys, a nice diagram, a few indexes.
No DTS, complex userstuff and that.
The target MSSQLServer will be 2000.
So now I need to know how to get my databaseschema and content from 7 to
2000.
As far as I can tell the option: GENERATE SQL only offers me an text-based
instruction for SCHEMA, not the content of table.
Right?
Question: Will MSSQL2000 understand the instructions created by MSSQL7?
As for the data itself:
The only way to export the data in the tables from MSSQL7 to MSSQL2000 I
found is by backing the whole thing up, as a binary.
(Using 'all tasks' --> 'Backup database')
Question: Will MSSQL2000 read and understand this file?
And will I need the databaseschema as generated by the GENERATE SQL option?
Or will MSSQL2000 be able to get that from the binary export?
Is this the way to do it, or am I missing lots of stuff?
Thanks for your time
Regards,
Erwin Moller
PS: I am sorry, but expect this is a very basic question. I just cannot find
any clear material on the subject online.> I am building an application that uses MSSQL7.
> Only basic stuff: 20 tables, foreign keys, a nice diagram, a few indexes.
> No DTS, complex userstuff and that.
> The target MSSQLServer will be 2000.
> So now I need to know how to get my databaseschema and content from 7 to
> 2000.
> As far as I can tell the option: GENERATE SQL only offers me an text-based
> instruction for SCHEMA, not the content of table.
> Right?
Right.
> Question: Will MSSQL2000 understand the instructions created by MSSQL7?
Yes.
> As for the data itself:
> The only way to export the data in the tables from MSSQL7 to MSSQL2000 I
> found is by backing the whole thing up, as a binary.
> (Using 'all tasks' --> 'Backup database')
You found the easiest way. You could use Data transformation Services (DTS),
for example, as well.
> Question: Will MSSQL2000 read and understand this file?
Yes, simply restore the backup on SQL 2000 box. But I guess you will have to
change the physical path to data and log files, unless you have created the
database in 7.0 in your custom (not SQL default) folder and you have the
same directory structure in 2000.
> And will I need the databaseschema as generated by the GENERATE SQL
> option?
No.
> Or will MSSQL2000 be able to get that from the binary export?
Yes - backup has everything, schema and data.
> Is this the way to do it, or am I missing lots of stuff?
Yes, this is a good way. You have original 7.0 db, backup and new 2000 db
after the action. So. if anything goes wrong, you have 3 copies. And the
process is quite simple.
Dejan Sarka, SQL Server MVP
Mentor
www.SolidQualityLearning.com|||Thanks Dejan Sarka!
I seldom receive such to-the-point answers. :-)
Regards,
Erwin Moller
[First time in, so feel free to shoot me if needed]
I am experienced with Postgresql, but relatively new to MSSQLServer.
I am building an application that uses MSSQL7.
Only basic stuff: 20 tables, foreign keys, a nice diagram, a few indexes.
No DTS, complex userstuff and that.
The target MSSQLServer will be 2000.
So now I need to know how to get my databaseschema and content from 7 to
2000.
As far as I can tell the option: GENERATE SQL only offers me an text-based
instruction for SCHEMA, not the content of table.
Right?
Question: Will MSSQL2000 understand the instructions created by MSSQL7?
As for the data itself:
The only way to export the data in the tables from MSSQL7 to MSSQL2000 I
found is by backing the whole thing up, as a binary.
(Using 'all tasks' --> 'Backup database')
Question: Will MSSQL2000 read and understand this file?
And will I need the databaseschema as generated by the GENERATE SQL option?
Or will MSSQL2000 be able to get that from the binary export?
Is this the way to do it, or am I missing lots of stuff?
Thanks for your time
Regards,
Erwin Moller
PS: I am sorry, but expect this is a very basic question. I just cannot find
any clear material on the subject online.> I am building an application that uses MSSQL7.
> Only basic stuff: 20 tables, foreign keys, a nice diagram, a few indexes.
> No DTS, complex userstuff and that.
> The target MSSQLServer will be 2000.
> So now I need to know how to get my databaseschema and content from 7 to
> 2000.
> As far as I can tell the option: GENERATE SQL only offers me an text-based
> instruction for SCHEMA, not the content of table.
> Right?
Right.
> Question: Will MSSQL2000 understand the instructions created by MSSQL7?
Yes.
> As for the data itself:
> The only way to export the data in the tables from MSSQL7 to MSSQL2000 I
> found is by backing the whole thing up, as a binary.
> (Using 'all tasks' --> 'Backup database')
You found the easiest way. You could use Data transformation Services (DTS),
for example, as well.
> Question: Will MSSQL2000 read and understand this file?
Yes, simply restore the backup on SQL 2000 box. But I guess you will have to
change the physical path to data and log files, unless you have created the
database in 7.0 in your custom (not SQL default) folder and you have the
same directory structure in 2000.
> And will I need the databaseschema as generated by the GENERATE SQL
> option?
No.
> Or will MSSQL2000 be able to get that from the binary export?
Yes - backup has everything, schema and data.
> Is this the way to do it, or am I missing lots of stuff?
Yes, this is a good way. You have original 7.0 db, backup and new 2000 db
after the action. So. if anything goes wrong, you have 3 copies. And the
process is quite simple.
Dejan Sarka, SQL Server MVP
Mentor
www.SolidQualityLearning.com|||Thanks Dejan Sarka!
I seldom receive such to-the-point answers. :-)
Regards,
Erwin Moller
MSSQL7 -> MSSQL2000 schema and data
Hi group,
[First time in, so feel free to shoot me if needed]
I am experienced with Postgresql, but relatively new to MSSQLServer.
I am building an application that uses MSSQL7.
Only basic stuff: 20 tables, foreign keys, a nice diagram, a few indexes.
No DTS, complex userstuff and that.
The target MSSQLServer will be 2000.
So now I need to know how to get my databaseschema and content from 7 to
2000.
As far as I can tell the option: GENERATE SQL only offers me an text-based
instruction for SCHEMA, not the content of table.
Right?
Question: Will MSSQL2000 understand the instructions created by MSSQL7?
As for the data itself:
The only way to export the data in the tables from MSSQL7 to MSSQL2000 I
found is by backing the whole thing up, as a binary.
(Using 'all tasks' --> 'Backup database')
Question: Will MSSQL2000 read and understand this file?
And will I need the databaseschema as generated by the GENERATE SQL option?
Or will MSSQL2000 be able to get that from the binary export?
Is this the way to do it, or am I missing lots of stuff?
Thanks for your time
Regards,
Erwin Moller
PS: I am sorry, but expect this is a very basic question. I just cannot find
any clear material on the subject online.> I am building an application that uses MSSQL7.
> Only basic stuff: 20 tables, foreign keys, a nice diagram, a few indexes.
> No DTS, complex userstuff and that.
> The target MSSQLServer will be 2000.
> So now I need to know how to get my databaseschema and content from 7 to
> 2000.
> As far as I can tell the option: GENERATE SQL only offers me an text-based
> instruction for SCHEMA, not the content of table.
> Right?
Right.
> Question: Will MSSQL2000 understand the instructions created by MSSQL7?
Yes.
> As for the data itself:
> The only way to export the data in the tables from MSSQL7 to MSSQL2000 I
> found is by backing the whole thing up, as a binary.
> (Using 'all tasks' --> 'Backup database')
You found the easiest way. You could use Data transformation Services (DTS),
for example, as well.
> Question: Will MSSQL2000 read and understand this file?
Yes, simply restore the backup on SQL 2000 box. But I guess you will have to
change the physical path to data and log files, unless you have created the
database in 7.0 in your custom (not SQL default) folder and you have the
same directory structure in 2000.
> And will I need the databaseschema as generated by the GENERATE SQL
> option?
No.
> Or will MSSQL2000 be able to get that from the binary export?
Yes - backup has everything, schema and data.
> Is this the way to do it, or am I missing lots of stuff?
Yes, this is a good way. You have original 7.0 db, backup and new 2000 db
after the action. So. if anything goes wrong, you have 3 copies. And the
process is quite simple.
--
Dejan Sarka, SQL Server MVP
Mentor
www.SolidQualityLearning.com|||Thanks Dejan Sarka!
I seldom receive such to-the-point answers. :-)
Regards,
Erwin Moller
[First time in, so feel free to shoot me if needed]
I am experienced with Postgresql, but relatively new to MSSQLServer.
I am building an application that uses MSSQL7.
Only basic stuff: 20 tables, foreign keys, a nice diagram, a few indexes.
No DTS, complex userstuff and that.
The target MSSQLServer will be 2000.
So now I need to know how to get my databaseschema and content from 7 to
2000.
As far as I can tell the option: GENERATE SQL only offers me an text-based
instruction for SCHEMA, not the content of table.
Right?
Question: Will MSSQL2000 understand the instructions created by MSSQL7?
As for the data itself:
The only way to export the data in the tables from MSSQL7 to MSSQL2000 I
found is by backing the whole thing up, as a binary.
(Using 'all tasks' --> 'Backup database')
Question: Will MSSQL2000 read and understand this file?
And will I need the databaseschema as generated by the GENERATE SQL option?
Or will MSSQL2000 be able to get that from the binary export?
Is this the way to do it, or am I missing lots of stuff?
Thanks for your time
Regards,
Erwin Moller
PS: I am sorry, but expect this is a very basic question. I just cannot find
any clear material on the subject online.> I am building an application that uses MSSQL7.
> Only basic stuff: 20 tables, foreign keys, a nice diagram, a few indexes.
> No DTS, complex userstuff and that.
> The target MSSQLServer will be 2000.
> So now I need to know how to get my databaseschema and content from 7 to
> 2000.
> As far as I can tell the option: GENERATE SQL only offers me an text-based
> instruction for SCHEMA, not the content of table.
> Right?
Right.
> Question: Will MSSQL2000 understand the instructions created by MSSQL7?
Yes.
> As for the data itself:
> The only way to export the data in the tables from MSSQL7 to MSSQL2000 I
> found is by backing the whole thing up, as a binary.
> (Using 'all tasks' --> 'Backup database')
You found the easiest way. You could use Data transformation Services (DTS),
for example, as well.
> Question: Will MSSQL2000 read and understand this file?
Yes, simply restore the backup on SQL 2000 box. But I guess you will have to
change the physical path to data and log files, unless you have created the
database in 7.0 in your custom (not SQL default) folder and you have the
same directory structure in 2000.
> And will I need the databaseschema as generated by the GENERATE SQL
> option?
No.
> Or will MSSQL2000 be able to get that from the binary export?
Yes - backup has everything, schema and data.
> Is this the way to do it, or am I missing lots of stuff?
Yes, this is a good way. You have original 7.0 db, backup and new 2000 db
after the action. So. if anything goes wrong, you have 3 copies. And the
process is quite simple.
--
Dejan Sarka, SQL Server MVP
Mentor
www.SolidQualityLearning.com|||Thanks Dejan Sarka!
I seldom receive such to-the-point answers. :-)
Regards,
Erwin Moller
MSSQL2005 SP2 and DB-Lib Connection
We have some legacy processes written in C with embedded SQL. They were
compiled with MSSQL2000 libraries and used db-lib for database connections.
After the database was upgraded to MSSQL2005, they could still make the
connection. Recently we have applied MSSQL2005 service pack 2 on the test
server and these processes can no longer connect (error message: SQL Server
is unavailable or does not exist). All other apps using the native client
work OK. Is there anything I can do at the MSSQL side to allow those legacy
processes to connect? Thanks.
Wow... it's been awhile since I supported C and DBLib. I taught this at MSU
for 5 years or so but that was a LONG time ago...
Ok, consider that DBLib requires a matched set of the named pipes DLL and
the dblib dll. If these get out of sync then you're pooched.
I'm really surprised that you've been able to hold out this long. I would
get up on Connect and report a bug but I doubt if they support DBLib any
longer. I don't think there is anything you can do on the server side to fix
it--except rolling back SP2. I expect the tightened the TDS in some way that
made it incompatible with legacy DBLib apps.
hth
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"mason" <masonliu@.msn.com> wrote in message
news:O8MZ$FsdHHA.984@.TK2MSFTNGP04.phx.gbl...
> We have some legacy processes written in C with embedded SQL. They were
> compiled with MSSQL2000 libraries and used db-lib for database
> connections. After the database was upgraded to MSSQL2005, they could
> still make the connection. Recently we have applied MSSQL2005 service pack
> 2 on the test server and these processes can no longer connect (error
> message: SQL Server is unavailable or does not exist). All other apps
> using the native client work OK. Is there anything I can do at the MSSQL
> side to allow those legacy processes to connect? Thanks.
|||We will rewrite them if we have to, but if there is a way to give them
another life, ... Thanks.
"William (Bill) Vaughn" <billvaRemoveThis@.betav.com> wrote in message
news:ubW7bCudHHA.3272@.TK2MSFTNGP03.phx.gbl...[vbcol=seagreen]
> Wow... it's been awhile since I supported C and DBLib. I taught this at
> MSU for 5 years or so but that was a LONG time ago...
> Ok, consider that DBLib requires a matched set of the named pipes DLL and
> the dblib dll. If these get out of sync then you're pooched.
> I'm really surprised that you've been able to hold out this long. I would
> get up on Connect and report a bug but I doubt if they support DBLib any
> longer. I don't think there is anything you can do on the server side to
> fix it--except rolling back SP2. I expect the tightened the TDS in some
> way that made it incompatible with legacy DBLib apps.
> hth
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> INETA Speaker
> www.betav.com/blog/billva
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> __________________________________
> Visit www.hitchhikerguides.net to get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> ------
> "mason" <masonliu@.msn.com> wrote in message
> news:O8MZ$FsdHHA.984@.TK2MSFTNGP04.phx.gbl...
|||Did the test server work before you applied SP@. and did you also upgrade the
test server from SQL 2000? The reason I ask is that SQL Server 2005 doesn't
include the dblib dll anymore so the only way it would have worked is if the
dll was left over from SQL Server 2000.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"mason" <masonliu@.msn.com> wrote in message
news:O8MZ$FsdHHA.984@.TK2MSFTNGP04.phx.gbl...
> We have some legacy processes written in C with embedded SQL. They were
> compiled with MSSQL2000 libraries and used db-lib for database
> connections. After the database was upgraded to MSSQL2005, they could
> still make the connection. Recently we have applied MSSQL2005 service pack
> 2 on the test server and these processes can no longer connect (error
> message: SQL Server is unavailable or does not exist). All other apps
> using the native client work OK. Is there anything I can do at the MSSQL
> side to allow those legacy processes to connect? Thanks.
|||Yes. It worked with MSSQL2005 SP1. The test server was created from scratch
with MSSQL2005. We copied two DLLs (ntwdblib.dll and sqlakw32.dll) from
MSSQL2000 client.
"Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
news:70709573-251D-4E13-8F60-75AF6858DD62@.microsoft.com...
> Did the test server work before you applied SP@. and did you also upgrade
> the test server from SQL 2000? The reason I ask is that SQL Server 2005
> doesn't include the dblib dll anymore so the only way it would have worked
> is if the dll was left over from SQL Server 2000.
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "mason" <masonliu@.msn.com> wrote in message
> news:O8MZ$FsdHHA.984@.TK2MSFTNGP04.phx.gbl...
>
|||Did you register both DLLs?
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"mason" <masonliu@.msn.com> wrote in message
news:%2301l8PvdHHA.5056@.TK2MSFTNGP02.phx.gbl...
> Yes. It worked with MSSQL2005 SP1. The test server was created from
> scratch with MSSQL2005. We copied two DLLs (ntwdblib.dll and sqlakw32.dll)
> from MSSQL2000 client.
>
> "Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
> news:70709573-251D-4E13-8F60-75AF6858DD62@.microsoft.com...
>
|||No. Tried to register now and got error msgs such as
DllRegisterServer/DllInstall entry points not found.
Those processes are working fine under MSSQL2005 SP1 in production.
"William (Bill) Vaughn" <billvaRemoveThis@.betav.com> wrote in message
news:e4nA%23i5dHHA.984@.TK2MSFTNGP04.phx.gbl...[vbcol=seagreen]
> Did you register both DLLs?
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> INETA Speaker
> www.betav.com/blog/billva
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> __________________________________
> Visit www.hitchhikerguides.net to get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> ------
> "mason" <masonliu@.msn.com> wrote in message
> news:%2301l8PvdHHA.5056@.TK2MSFTNGP02.phx.gbl...
compiled with MSSQL2000 libraries and used db-lib for database connections.
After the database was upgraded to MSSQL2005, they could still make the
connection. Recently we have applied MSSQL2005 service pack 2 on the test
server and these processes can no longer connect (error message: SQL Server
is unavailable or does not exist). All other apps using the native client
work OK. Is there anything I can do at the MSSQL side to allow those legacy
processes to connect? Thanks.
Wow... it's been awhile since I supported C and DBLib. I taught this at MSU
for 5 years or so but that was a LONG time ago...
Ok, consider that DBLib requires a matched set of the named pipes DLL and
the dblib dll. If these get out of sync then you're pooched.
I'm really surprised that you've been able to hold out this long. I would
get up on Connect and report a bug but I doubt if they support DBLib any
longer. I don't think there is anything you can do on the server side to fix
it--except rolling back SP2. I expect the tightened the TDS in some way that
made it incompatible with legacy DBLib apps.
hth
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"mason" <masonliu@.msn.com> wrote in message
news:O8MZ$FsdHHA.984@.TK2MSFTNGP04.phx.gbl...
> We have some legacy processes written in C with embedded SQL. They were
> compiled with MSSQL2000 libraries and used db-lib for database
> connections. After the database was upgraded to MSSQL2005, they could
> still make the connection. Recently we have applied MSSQL2005 service pack
> 2 on the test server and these processes can no longer connect (error
> message: SQL Server is unavailable or does not exist). All other apps
> using the native client work OK. Is there anything I can do at the MSSQL
> side to allow those legacy processes to connect? Thanks.
|||We will rewrite them if we have to, but if there is a way to give them
another life, ... Thanks.
"William (Bill) Vaughn" <billvaRemoveThis@.betav.com> wrote in message
news:ubW7bCudHHA.3272@.TK2MSFTNGP03.phx.gbl...[vbcol=seagreen]
> Wow... it's been awhile since I supported C and DBLib. I taught this at
> MSU for 5 years or so but that was a LONG time ago...
> Ok, consider that DBLib requires a matched set of the named pipes DLL and
> the dblib dll. If these get out of sync then you're pooched.
> I'm really surprised that you've been able to hold out this long. I would
> get up on Connect and report a bug but I doubt if they support DBLib any
> longer. I don't think there is anything you can do on the server side to
> fix it--except rolling back SP2. I expect the tightened the TDS in some
> way that made it incompatible with legacy DBLib apps.
> hth
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> INETA Speaker
> www.betav.com/blog/billva
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> __________________________________
> Visit www.hitchhikerguides.net to get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> ------
> "mason" <masonliu@.msn.com> wrote in message
> news:O8MZ$FsdHHA.984@.TK2MSFTNGP04.phx.gbl...
|||Did the test server work before you applied SP@. and did you also upgrade the
test server from SQL 2000? The reason I ask is that SQL Server 2005 doesn't
include the dblib dll anymore so the only way it would have worked is if the
dll was left over from SQL Server 2000.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"mason" <masonliu@.msn.com> wrote in message
news:O8MZ$FsdHHA.984@.TK2MSFTNGP04.phx.gbl...
> We have some legacy processes written in C with embedded SQL. They were
> compiled with MSSQL2000 libraries and used db-lib for database
> connections. After the database was upgraded to MSSQL2005, they could
> still make the connection. Recently we have applied MSSQL2005 service pack
> 2 on the test server and these processes can no longer connect (error
> message: SQL Server is unavailable or does not exist). All other apps
> using the native client work OK. Is there anything I can do at the MSSQL
> side to allow those legacy processes to connect? Thanks.
|||Yes. It worked with MSSQL2005 SP1. The test server was created from scratch
with MSSQL2005. We copied two DLLs (ntwdblib.dll and sqlakw32.dll) from
MSSQL2000 client.
"Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
news:70709573-251D-4E13-8F60-75AF6858DD62@.microsoft.com...
> Did the test server work before you applied SP@. and did you also upgrade
> the test server from SQL 2000? The reason I ask is that SQL Server 2005
> doesn't include the dblib dll anymore so the only way it would have worked
> is if the dll was left over from SQL Server 2000.
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "mason" <masonliu@.msn.com> wrote in message
> news:O8MZ$FsdHHA.984@.TK2MSFTNGP04.phx.gbl...
>
|||Did you register both DLLs?
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"mason" <masonliu@.msn.com> wrote in message
news:%2301l8PvdHHA.5056@.TK2MSFTNGP02.phx.gbl...
> Yes. It worked with MSSQL2005 SP1. The test server was created from
> scratch with MSSQL2005. We copied two DLLs (ntwdblib.dll and sqlakw32.dll)
> from MSSQL2000 client.
>
> "Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
> news:70709573-251D-4E13-8F60-75AF6858DD62@.microsoft.com...
>
|||No. Tried to register now and got error msgs such as
DllRegisterServer/DllInstall entry points not found.
Those processes are working fine under MSSQL2005 SP1 in production.
"William (Bill) Vaughn" <billvaRemoveThis@.betav.com> wrote in message
news:e4nA%23i5dHHA.984@.TK2MSFTNGP04.phx.gbl...[vbcol=seagreen]
> Did you register both DLLs?
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> INETA Speaker
> www.betav.com/blog/billva
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> __________________________________
> Visit www.hitchhikerguides.net to get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> ------
> "mason" <masonliu@.msn.com> wrote in message
> news:%2301l8PvdHHA.5056@.TK2MSFTNGP02.phx.gbl...
MSSQL2005 SP2 and DB-Lib Connection
We have some legacy processes written in C with embedded SQL. They were
compiled with MSSQL2000 libraries and used db-lib for database connections.
After the database was upgraded to MSSQL2005, they could still make the
connection. Recently we have applied MSSQL2005 service pack 2 on the test
server and these processes can no longer connect (error message: SQL Server
is unavailable or does not exist). All other apps using the native client
work OK. Is there anything I can do at the MSSQL side to allow those legacy
processes to connect? Thanks.Wow... it's been awhile since I supported C and DBLib. I taught this at MSU
for 5 years or so but that was a LONG time ago...
Ok, consider that DBLib requires a matched set of the named pipes DLL and
the dblib dll. If these get out of sync then you're pooched.
I'm really surprised that you've been able to hold out this long. I would
get up on Connect and report a bug but I doubt if they support DBLib any
longer. I don't think there is anything you can do on the server side to fix
it--except rolling back SP2. I expect the tightened the TDS in some way that
made it incompatible with legacy DBLib apps.
hth
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
----
---
"mason" <masonliu@.msn.com> wrote in message
news:O8MZ$FsdHHA.984@.TK2MSFTNGP04.phx.gbl...
> We have some legacy processes written in C with embedded SQL. They were
> compiled with MSSQL2000 libraries and used db-lib for database
> connections. After the database was upgraded to MSSQL2005, they could
> still make the connection. Recently we have applied MSSQL2005 service pack
> 2 on the test server and these processes can no longer connect (error
> message: SQL Server is unavailable or does not exist). All other apps
> using the native client work OK. Is there anything I can do at the MSSQL
> side to allow those legacy processes to connect? Thanks.|||We will rewrite them if we have to, but if there is a way to give them
another life, ... Thanks.
"William (Bill) Vaughn" <billvaRemoveThis@.betav.com> wrote in message
news:ubW7bCudHHA.3272@.TK2MSFTNGP03.phx.gbl...[vbcol=seagreen]
> Wow... it's been awhile since I supported C and DBLib. I taught this at
> MSU for 5 years or so but that was a LONG time ago...
> Ok, consider that DBLib requires a matched set of the named pipes DLL and
> the dblib dll. If these get out of sync then you're pooched.
> I'm really surprised that you've been able to hold out this long. I would
> get up on Connect and report a bug but I doubt if they support DBLib any
> longer. I don't think there is anything you can do on the server side to
> fix it--except rolling back SP2. I expect the tightened the TDS in some
> way that made it incompatible with legacy DBLib apps.
> hth
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> INETA Speaker
> www.betav.com/blog/billva
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> __________________________________
> Visit www.hitchhikerguides.net to get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> ----
---
> "mason" <masonliu@.msn.com> wrote in message
> news:O8MZ$FsdHHA.984@.TK2MSFTNGP04.phx.gbl...|||Did the test server work before you applied SP@. and did you also upgrade the
test server from SQL 2000? The reason I ask is that SQL Server 2005 doesn't
include the dblib dll anymore so the only way it would have worked is if the
dll was left over from SQL Server 2000.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"mason" <masonliu@.msn.com> wrote in message
news:O8MZ$FsdHHA.984@.TK2MSFTNGP04.phx.gbl...
> We have some legacy processes written in C with embedded SQL. They were
> compiled with MSSQL2000 libraries and used db-lib for database
> connections. After the database was upgraded to MSSQL2005, they could
> still make the connection. Recently we have applied MSSQL2005 service pack
> 2 on the test server and these processes can no longer connect (error
> message: SQL Server is unavailable or does not exist). All other apps
> using the native client work OK. Is there anything I can do at the MSSQL
> side to allow those legacy processes to connect? Thanks.|||Yes. It worked with MSSQL2005 SP1. The test server was created from scratch
with MSSQL2005. We copied two DLLs (ntwdblib.dll and sqlakw32.dll) from
MSSQL2000 client.
"Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
news:70709573-251D-4E13-8F60-75AF6858DD62@.microsoft.com...
> Did the test server work before you applied SP@. and did you also upgrade
> the test server from SQL 2000? The reason I ask is that SQL Server 2005
> doesn't include the dblib dll anymore so the only way it would have worked
> is if the dll was left over from SQL Server 2000.
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "mason" <masonliu@.msn.com> wrote in message
> news:O8MZ$FsdHHA.984@.TK2MSFTNGP04.phx.gbl...
>|||Did you register both DLLs?
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
----
---
"mason" <masonliu@.msn.com> wrote in message
news:%2301l8PvdHHA.5056@.TK2MSFTNGP02.phx.gbl...
> Yes. It worked with MSSQL2005 SP1. The test server was created from
> scratch with MSSQL2005. We copied two DLLs (ntwdblib.dll and sqlakw32.dll)
> from MSSQL2000 client.
>
> "Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
> news:70709573-251D-4E13-8F60-75AF6858DD62@.microsoft.com...
>|||No. Tried to register now and got error msgs such as
DllRegisterServer/DllInstall entry points not found.
Those processes are working fine under MSSQL2005 SP1 in production.
"William (Bill) Vaughn" <billvaRemoveThis@.betav.com> wrote in message
news:e4nA%23i5dHHA.984@.TK2MSFTNGP04.phx.gbl...[vbcol=seagreen]
> Did you register both DLLs?
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> INETA Speaker
> www.betav.com/blog/billva
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> __________________________________
> Visit www.hitchhikerguides.net to get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> ----
---
> "mason" <masonliu@.msn.com> wrote in message
> news:%2301l8PvdHHA.5056@.TK2MSFTNGP02.phx.gbl...
compiled with MSSQL2000 libraries and used db-lib for database connections.
After the database was upgraded to MSSQL2005, they could still make the
connection. Recently we have applied MSSQL2005 service pack 2 on the test
server and these processes can no longer connect (error message: SQL Server
is unavailable or does not exist). All other apps using the native client
work OK. Is there anything I can do at the MSSQL side to allow those legacy
processes to connect? Thanks.Wow... it's been awhile since I supported C and DBLib. I taught this at MSU
for 5 years or so but that was a LONG time ago...
Ok, consider that DBLib requires a matched set of the named pipes DLL and
the dblib dll. If these get out of sync then you're pooched.
I'm really surprised that you've been able to hold out this long. I would
get up on Connect and report a bug but I doubt if they support DBLib any
longer. I don't think there is anything you can do on the server side to fix
it--except rolling back SP2. I expect the tightened the TDS in some way that
made it incompatible with legacy DBLib apps.
hth
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
----
---
"mason" <masonliu@.msn.com> wrote in message
news:O8MZ$FsdHHA.984@.TK2MSFTNGP04.phx.gbl...
> We have some legacy processes written in C with embedded SQL. They were
> compiled with MSSQL2000 libraries and used db-lib for database
> connections. After the database was upgraded to MSSQL2005, they could
> still make the connection. Recently we have applied MSSQL2005 service pack
> 2 on the test server and these processes can no longer connect (error
> message: SQL Server is unavailable or does not exist). All other apps
> using the native client work OK. Is there anything I can do at the MSSQL
> side to allow those legacy processes to connect? Thanks.|||We will rewrite them if we have to, but if there is a way to give them
another life, ... Thanks.
"William (Bill) Vaughn" <billvaRemoveThis@.betav.com> wrote in message
news:ubW7bCudHHA.3272@.TK2MSFTNGP03.phx.gbl...[vbcol=seagreen]
> Wow... it's been awhile since I supported C and DBLib. I taught this at
> MSU for 5 years or so but that was a LONG time ago...
> Ok, consider that DBLib requires a matched set of the named pipes DLL and
> the dblib dll. If these get out of sync then you're pooched.
> I'm really surprised that you've been able to hold out this long. I would
> get up on Connect and report a bug but I doubt if they support DBLib any
> longer. I don't think there is anything you can do on the server side to
> fix it--except rolling back SP2. I expect the tightened the TDS in some
> way that made it incompatible with legacy DBLib apps.
> hth
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> INETA Speaker
> www.betav.com/blog/billva
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> __________________________________
> Visit www.hitchhikerguides.net to get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> ----
---
> "mason" <masonliu@.msn.com> wrote in message
> news:O8MZ$FsdHHA.984@.TK2MSFTNGP04.phx.gbl...|||Did the test server work before you applied SP@. and did you also upgrade the
test server from SQL 2000? The reason I ask is that SQL Server 2005 doesn't
include the dblib dll anymore so the only way it would have worked is if the
dll was left over from SQL Server 2000.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"mason" <masonliu@.msn.com> wrote in message
news:O8MZ$FsdHHA.984@.TK2MSFTNGP04.phx.gbl...
> We have some legacy processes written in C with embedded SQL. They were
> compiled with MSSQL2000 libraries and used db-lib for database
> connections. After the database was upgraded to MSSQL2005, they could
> still make the connection. Recently we have applied MSSQL2005 service pack
> 2 on the test server and these processes can no longer connect (error
> message: SQL Server is unavailable or does not exist). All other apps
> using the native client work OK. Is there anything I can do at the MSSQL
> side to allow those legacy processes to connect? Thanks.|||Yes. It worked with MSSQL2005 SP1. The test server was created from scratch
with MSSQL2005. We copied two DLLs (ntwdblib.dll and sqlakw32.dll) from
MSSQL2000 client.
"Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
news:70709573-251D-4E13-8F60-75AF6858DD62@.microsoft.com...
> Did the test server work before you applied SP@. and did you also upgrade
> the test server from SQL 2000? The reason I ask is that SQL Server 2005
> doesn't include the dblib dll anymore so the only way it would have worked
> is if the dll was left over from SQL Server 2000.
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "mason" <masonliu@.msn.com> wrote in message
> news:O8MZ$FsdHHA.984@.TK2MSFTNGP04.phx.gbl...
>|||Did you register both DLLs?
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
----
---
"mason" <masonliu@.msn.com> wrote in message
news:%2301l8PvdHHA.5056@.TK2MSFTNGP02.phx.gbl...
> Yes. It worked with MSSQL2005 SP1. The test server was created from
> scratch with MSSQL2005. We copied two DLLs (ntwdblib.dll and sqlakw32.dll)
> from MSSQL2000 client.
>
> "Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
> news:70709573-251D-4E13-8F60-75AF6858DD62@.microsoft.com...
>|||No. Tried to register now and got error msgs such as
DllRegisterServer/DllInstall entry points not found.
Those processes are working fine under MSSQL2005 SP1 in production.
"William (Bill) Vaughn" <billvaRemoveThis@.betav.com> wrote in message
news:e4nA%23i5dHHA.984@.TK2MSFTNGP04.phx.gbl...[vbcol=seagreen]
> Did you register both DLLs?
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> INETA Speaker
> www.betav.com/blog/billva
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> __________________________________
> Visit www.hitchhikerguides.net to get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> ----
---
> "mason" <masonliu@.msn.com> wrote in message
> news:%2301l8PvdHHA.5056@.TK2MSFTNGP02.phx.gbl...
Wednesday, March 7, 2012
mssql2005
how do I bring files from mssql2000 to mssql2005? A BAK from 2000 doesnt
seem to work as it did in mssql97 & 2000
thanks,
Raul Rego
NJPIES> A BAK from 2000 doesnt seem to work as it did in mssql97 & 2000
It should do. You can both restore a 2000 backup into 2005 and also attach a
2000 database (mdf etc
files) into 2005. What error message do you get?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"news.microsoft.com" <jjkgr@.hotmail.com> wrote in message
news:u0s8ppDzGHA.4232@.TK2MSFTNGP04.phx.gbl...
> how do I bring files from mssql2000 to mssql2005? A BAK from 2000 doesnt
seem to work as it did
> in mssql97 & 2000
> thanks,
> Raul Rego
> NJPIES
>
seem to work as it did in mssql97 & 2000
thanks,
Raul Rego
NJPIES> A BAK from 2000 doesnt seem to work as it did in mssql97 & 2000
It should do. You can both restore a 2000 backup into 2005 and also attach a
2000 database (mdf etc
files) into 2005. What error message do you get?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"news.microsoft.com" <jjkgr@.hotmail.com> wrote in message
news:u0s8ppDzGHA.4232@.TK2MSFTNGP04.phx.gbl...
> how do I bring files from mssql2000 to mssql2005? A BAK from 2000 doesnt
seem to work as it did
> in mssql97 & 2000
> thanks,
> Raul Rego
> NJPIES
>
mssql2005
how do I bring files from mssql2000 to mssql2005? A BAK from 2000 doesnt
seem to work as it did in mssql97 & 2000
thanks,
Raul Rego
NJPIES> A BAK from 2000 doesnt seem to work as it did in mssql97 & 2000
It should do. You can both restore a 2000 backup into 2005 and also attach a 2000 database (mdf etc
files) into 2005. What error message do you get?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"news.microsoft.com" <jjkgr@.hotmail.com> wrote in message
news:u0s8ppDzGHA.4232@.TK2MSFTNGP04.phx.gbl...
> how do I bring files from mssql2000 to mssql2005? A BAK from 2000 doesnt seem to work as it did
> in mssql97 & 2000
> thanks,
> Raul Rego
> NJPIES
>
seem to work as it did in mssql97 & 2000
thanks,
Raul Rego
NJPIES> A BAK from 2000 doesnt seem to work as it did in mssql97 & 2000
It should do. You can both restore a 2000 backup into 2005 and also attach a 2000 database (mdf etc
files) into 2005. What error message do you get?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"news.microsoft.com" <jjkgr@.hotmail.com> wrote in message
news:u0s8ppDzGHA.4232@.TK2MSFTNGP04.phx.gbl...
> how do I bring files from mssql2000 to mssql2005? A BAK from 2000 doesnt seem to work as it did
> in mssql97 & 2000
> thanks,
> Raul Rego
> NJPIES
>
msSQL2000 to mssql2005
I have set up a replication between mssql2000 to mssql2005
Mssql2000 is the publisher and mssql is subscriber.
And it work fine.
Then I remove the publication because I need to do spm Alter statement
against Tables in the database
When I try to add subscription
with @.sync_type = N'none' (In This case the data i alredy in the subscribers
databse)
I get theese error:
Violation of PRIMARY KEY constraint 'PK__@.snapshot_seqnos__328568A3'.
Cannot insert duplicate key in object '#3191446A'.
(Source: SRVIQDB03 (Data source); Error number: 2627)
Her is Add subscr.
use [Tellus_DB209]
exec sp_addsubscription @.publication = N'pub_Tellus_DB209_2005',
@.subscriber = N'RDASP21', @.destination_db = N'Tellus',
@.subscription_type = N'Push', @.sync_type = N'none',
@.article = N'all', @.update_mode = N'read only',
@.loopback_detection = N'True',
@.frequency_type = 64, @.frequency_interval = 0, @.frequency_relative_interval
= 0,
@.frequency_recurrence_factor = 0, @.frequency_subday = 0,
@.frequency_subday_interval = 0,
@.active_start_time_of_day = 0, @.active_end_time_of_day = 235959,
@.active_start_date = 20060202, @.active_end_date = 99991231, @.offloadagent =
0,
@.enabled_for_syncmgr = N'False', @.dts_package_location = N'Distributor'
What is this about.
What sp is SQL 2000? You may need to check this link to fix the problem.
http://groups.google.com/group/micro...5?dmode=source
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Roger Nygrd" <roger@.askit.no> wrote in message
news:11u4op7pil83qf4@.corp.supernews.com...
>I have set up a replication between mssql2000 to mssql2005
> Mssql2000 is the publisher and mssql is subscriber.
> And it work fine.
> Then I remove the publication because I need to do spm Alter statement
> against Tables in the database
> When I try to add subscription
> with @.sync_type = N'none' (In This case the data i alredy in the
> subscribers databse)
> I get theese error:
> Violation of PRIMARY KEY constraint 'PK__@.snapshot_seqnos__328568A3'.
> Cannot insert duplicate key in object '#3191446A'.
> (Source: SRVIQDB03 (Data source); Error number: 2627)
> Her is Add subscr.
> use [Tellus_DB209]
> exec sp_addsubscription @.publication = N'pub_Tellus_DB209_2005',
> @.subscriber = N'RDASP21', @.destination_db = N'Tellus',
> @.subscription_type = N'Push', @.sync_type = N'none',
> @.article = N'all', @.update_mode = N'read only',
> @.loopback_detection = N'True',
> @.frequency_type = 64, @.frequency_interval = 0,
> @.frequency_relative_interval = 0,
> @.frequency_recurrence_factor = 0, @.frequency_subday = 0,
> @.frequency_subday_interval = 0,
> @.active_start_time_of_day = 0, @.active_end_time_of_day = 235959,
> @.active_start_date = 20060202, @.active_end_date = 99991231, @.offloadagent
> = 0,
> @.enabled_for_syncmgr = N'False', @.dts_package_location = N'Distributor'
> What is this about.
>
Mssql2000 is the publisher and mssql is subscriber.
And it work fine.
Then I remove the publication because I need to do spm Alter statement
against Tables in the database
When I try to add subscription
with @.sync_type = N'none' (In This case the data i alredy in the subscribers
databse)
I get theese error:
Violation of PRIMARY KEY constraint 'PK__@.snapshot_seqnos__328568A3'.
Cannot insert duplicate key in object '#3191446A'.
(Source: SRVIQDB03 (Data source); Error number: 2627)
Her is Add subscr.
use [Tellus_DB209]
exec sp_addsubscription @.publication = N'pub_Tellus_DB209_2005',
@.subscriber = N'RDASP21', @.destination_db = N'Tellus',
@.subscription_type = N'Push', @.sync_type = N'none',
@.article = N'all', @.update_mode = N'read only',
@.loopback_detection = N'True',
@.frequency_type = 64, @.frequency_interval = 0, @.frequency_relative_interval
= 0,
@.frequency_recurrence_factor = 0, @.frequency_subday = 0,
@.frequency_subday_interval = 0,
@.active_start_time_of_day = 0, @.active_end_time_of_day = 235959,
@.active_start_date = 20060202, @.active_end_date = 99991231, @.offloadagent =
0,
@.enabled_for_syncmgr = N'False', @.dts_package_location = N'Distributor'
What is this about.
What sp is SQL 2000? You may need to check this link to fix the problem.
http://groups.google.com/group/micro...5?dmode=source
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Roger Nygrd" <roger@.askit.no> wrote in message
news:11u4op7pil83qf4@.corp.supernews.com...
>I have set up a replication between mssql2000 to mssql2005
> Mssql2000 is the publisher and mssql is subscriber.
> And it work fine.
> Then I remove the publication because I need to do spm Alter statement
> against Tables in the database
> When I try to add subscription
> with @.sync_type = N'none' (In This case the data i alredy in the
> subscribers databse)
> I get theese error:
> Violation of PRIMARY KEY constraint 'PK__@.snapshot_seqnos__328568A3'.
> Cannot insert duplicate key in object '#3191446A'.
> (Source: SRVIQDB03 (Data source); Error number: 2627)
> Her is Add subscr.
> use [Tellus_DB209]
> exec sp_addsubscription @.publication = N'pub_Tellus_DB209_2005',
> @.subscriber = N'RDASP21', @.destination_db = N'Tellus',
> @.subscription_type = N'Push', @.sync_type = N'none',
> @.article = N'all', @.update_mode = N'read only',
> @.loopback_detection = N'True',
> @.frequency_type = 64, @.frequency_interval = 0,
> @.frequency_relative_interval = 0,
> @.frequency_recurrence_factor = 0, @.frequency_subday = 0,
> @.frequency_subday_interval = 0,
> @.active_start_time_of_day = 0, @.active_end_time_of_day = 235959,
> @.active_start_date = 20060202, @.active_end_date = 99991231, @.offloadagent
> = 0,
> @.enabled_for_syncmgr = N'False', @.dts_package_location = N'Distributor'
> What is this about.
>
mssql2000 on emc mirrorview volume
Hello!
Does anybody know whether mssql2000 and emc mirrorvew _certified_ for
joint work?
(Mirrorview is a fc-based remote mirroring solution)
I mean is it supported from the MS point of view to put mssql
datafiles on emc mirrorview volumes?
For example Oracle corp. has "Oracle Compatible Remote Mirroring
Technologies" certification.
But what about MS?inq_3@.hotmail.com (Inquisitive) wrote in message news:<85197477.0407110459.26c9b313@.posting.google.com>...
> Hello!
> Does anybody know whether mssql2000 and emc mirrorvew _certified_ for
> joint work?
> (Mirrorview is a fc-based remote mirroring solution)
> I mean is it supported from the MS point of view to put mssql
> datafiles on emc mirrorview volumes?
> For example Oracle corp. has "Oracle Compatible Remote Mirroring
> Technologies" certification.
> But what about MS?
I have no idea about that specific piece of hardware, but you might
want to ask EMC if it's certified for use with MSSQL (or indeed ask
Microsoft also). Microsoft's attitude appears to be that you can use
any hardware you want, but if it's not WHQL certified, then problems
will be referred back to the vendor:
http://support.microsoft.com/defaul...1&Product=sql2k
You could also want to look at "Snapshot Backups" in Books Online, if
that's relevant to what you're trying to do.
Simon
MSSQL2000 Maximum Memory
Hi,
I want to use MSSQL2000 on a server with 8GB ram amount.
Is there a way to use this ram under Win2003 Server?
What version of MSSQL2000 do I have to use?
thx
reinhold
Hi
You need to use:
Windows 2003 Enterprise Edition
SQL Server 2000 Enterprise Edition
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Reinhold" wrote:
> Hi,
> I want to use MSSQL2000 on a server with 8GB ram amount.
> Is there a way to use this ram under Win2003 Server?
> What version of MSSQL2000 do I have to use?
> thx
> reinhold
>
>
|||See if this helps:
http://support.microsoft.com/default...274750&sd=tech
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Reinhold" <reinholderlacher@.msn.com> wrote in message
news:OrbtVcisFHA.3424@.TK2MSFTNGP14.phx.gbl...
Hi,
I want to use MSSQL2000 on a server with 8GB ram amount.
Is there a way to use this ram under Win2003 Server?
What version of MSSQL2000 do I have to use?
thx
reinhold
|||> I want to use MSSQL2000 on a server with 8GB ram amount.
> Is there a way to use this ram under Win2003 Server?
Assuming 32-bit, you need Windows 2003 Server Enterprise Edition and SQL
Server Enterprise Edition. SQL Server AWE needs to be enabled to address
over 3GB. Windows 2003 Standard has a 4GB max memory limitation and SQL
Server Standard is limited to 2Gb.
Windows 2003 system requirements:
http://www.microsoft.com/windowsserv...s/default.mspx
How to configure memory for more than 2 GB in SQL Server:
http://support.microsoft.com/default...b;en-us;274750
Hope this helps.
Dan Guzman
SQL Server MVP
"Reinhold" <reinholderlacher@.msn.com> wrote in message
news:OrbtVcisFHA.3424@.TK2MSFTNGP14.phx.gbl...
> Hi,
> I want to use MSSQL2000 on a server with 8GB ram amount.
> Is there a way to use this ram under Win2003 Server?
> What version of MSSQL2000 do I have to use?
> thx
> reinhold
>
I want to use MSSQL2000 on a server with 8GB ram amount.
Is there a way to use this ram under Win2003 Server?
What version of MSSQL2000 do I have to use?
thx
reinhold
Hi
You need to use:
Windows 2003 Enterprise Edition
SQL Server 2000 Enterprise Edition
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Reinhold" wrote:
> Hi,
> I want to use MSSQL2000 on a server with 8GB ram amount.
> Is there a way to use this ram under Win2003 Server?
> What version of MSSQL2000 do I have to use?
> thx
> reinhold
>
>
|||See if this helps:
http://support.microsoft.com/default...274750&sd=tech
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Reinhold" <reinholderlacher@.msn.com> wrote in message
news:OrbtVcisFHA.3424@.TK2MSFTNGP14.phx.gbl...
Hi,
I want to use MSSQL2000 on a server with 8GB ram amount.
Is there a way to use this ram under Win2003 Server?
What version of MSSQL2000 do I have to use?
thx
reinhold
|||> I want to use MSSQL2000 on a server with 8GB ram amount.
> Is there a way to use this ram under Win2003 Server?
Assuming 32-bit, you need Windows 2003 Server Enterprise Edition and SQL
Server Enterprise Edition. SQL Server AWE needs to be enabled to address
over 3GB. Windows 2003 Standard has a 4GB max memory limitation and SQL
Server Standard is limited to 2Gb.
Windows 2003 system requirements:
http://www.microsoft.com/windowsserv...s/default.mspx
How to configure memory for more than 2 GB in SQL Server:
http://support.microsoft.com/default...b;en-us;274750
Hope this helps.
Dan Guzman
SQL Server MVP
"Reinhold" <reinholderlacher@.msn.com> wrote in message
news:OrbtVcisFHA.3424@.TK2MSFTNGP14.phx.gbl...
> Hi,
> I want to use MSSQL2000 on a server with 8GB ram amount.
> Is there a way to use this ram under Win2003 Server?
> What version of MSSQL2000 do I have to use?
> thx
> reinhold
>
MSSQL2000 Maximum Memory
Hi,
I want to use MSSQL2000 on a server with 8GB ram amount.
Is there a way to use this ram under Win2003 Server?
What version of MSSQL2000 do I have to use?
thx
reinholdHi
You need to use:
Windows 2003 Enterprise Edition
SQL Server 2000 Enterprise Edition
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Reinhold" wrote:
> Hi,
> I want to use MSSQL2000 on a server with 8GB ram amount.
> Is there a way to use this ram under Win2003 Server?
> What version of MSSQL2000 do I have to use?
> thx
> reinhold
>
>|||See if this helps:
http://support.microsoft.com/defaul...;274750&sd=tech
--
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Reinhold" <reinholderlacher@.msn.com> wrote in message
news:OrbtVcisFHA.3424@.TK2MSFTNGP14.phx.gbl...
Hi,
I want to use MSSQL2000 on a server with 8GB ram amount.
Is there a way to use this ram under Win2003 Server?
What version of MSSQL2000 do I have to use?
thx
reinhold|||> I want to use MSSQL2000 on a server with 8GB ram amount.
> Is there a way to use this ram under Win2003 Server?
Assuming 32-bit, you need Windows 2003 Server Enterprise Edition and SQL
Server Enterprise Edition. SQL Server AWE needs to be enabled to address
over 3GB. Windows 2003 Standard has a 4GB max memory limitation and SQL
Server Standard is limited to 2Gb.
Windows 2003 system requirements:
http://www.microsoft.com/windowsser...qs/default.mspx
How to configure memory for more than 2 GB in SQL Server:
http://support.microsoft.com/defaul...kb;en-us;274750
Hope this helps.
Dan Guzman
SQL Server MVP
"Reinhold" <reinholderlacher@.msn.com> wrote in message
news:OrbtVcisFHA.3424@.TK2MSFTNGP14.phx.gbl...
> Hi,
> I want to use MSSQL2000 on a server with 8GB ram amount.
> Is there a way to use this ram under Win2003 Server?
> What version of MSSQL2000 do I have to use?
> thx
> reinhold
>
I want to use MSSQL2000 on a server with 8GB ram amount.
Is there a way to use this ram under Win2003 Server?
What version of MSSQL2000 do I have to use?
thx
reinholdHi
You need to use:
Windows 2003 Enterprise Edition
SQL Server 2000 Enterprise Edition
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Reinhold" wrote:
> Hi,
> I want to use MSSQL2000 on a server with 8GB ram amount.
> Is there a way to use this ram under Win2003 Server?
> What version of MSSQL2000 do I have to use?
> thx
> reinhold
>
>|||See if this helps:
http://support.microsoft.com/defaul...;274750&sd=tech
--
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Reinhold" <reinholderlacher@.msn.com> wrote in message
news:OrbtVcisFHA.3424@.TK2MSFTNGP14.phx.gbl...
Hi,
I want to use MSSQL2000 on a server with 8GB ram amount.
Is there a way to use this ram under Win2003 Server?
What version of MSSQL2000 do I have to use?
thx
reinhold|||> I want to use MSSQL2000 on a server with 8GB ram amount.
> Is there a way to use this ram under Win2003 Server?
Assuming 32-bit, you need Windows 2003 Server Enterprise Edition and SQL
Server Enterprise Edition. SQL Server AWE needs to be enabled to address
over 3GB. Windows 2003 Standard has a 4GB max memory limitation and SQL
Server Standard is limited to 2Gb.
Windows 2003 system requirements:
http://www.microsoft.com/windowsser...qs/default.mspx
How to configure memory for more than 2 GB in SQL Server:
http://support.microsoft.com/defaul...kb;en-us;274750
Hope this helps.
Dan Guzman
SQL Server MVP
"Reinhold" <reinholderlacher@.msn.com> wrote in message
news:OrbtVcisFHA.3424@.TK2MSFTNGP14.phx.gbl...
> Hi,
> I want to use MSSQL2000 on a server with 8GB ram amount.
> Is there a way to use this ram under Win2003 Server?
> What version of MSSQL2000 do I have to use?
> thx
> reinhold
>
MSSQL2000 Maximum Memory
Hi,
I want to use MSSQL2000 on a server with 8GB ram amount.
Is there a way to use this ram under Win2003 Server?
What version of MSSQL2000 do I have to use?
thx
reinholdHi
You need to use:
Windows 2003 Enterprise Edition
SQL Server 2000 Enterprise Edition
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Reinhold" wrote:
> Hi,
> I want to use MSSQL2000 on a server with 8GB ram amount.
> Is there a way to use this ram under Win2003 Server?
> What version of MSSQL2000 do I have to use?
> thx
> reinhold
>
>|||See if this helps:
http://support.microsoft.com/default.aspx?scid=kb;en-us;274750&sd=tech
--
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Reinhold" <reinholderlacher@.msn.com> wrote in message
news:OrbtVcisFHA.3424@.TK2MSFTNGP14.phx.gbl...
Hi,
I want to use MSSQL2000 on a server with 8GB ram amount.
Is there a way to use this ram under Win2003 Server?
What version of MSSQL2000 do I have to use?
thx
reinhold|||> I want to use MSSQL2000 on a server with 8GB ram amount.
> Is there a way to use this ram under Win2003 Server?
Assuming 32-bit, you need Windows 2003 Server Enterprise Edition and SQL
Server Enterprise Edition. SQL Server AWE needs to be enabled to address
over 3GB. Windows 2003 Standard has a 4GB max memory limitation and SQL
Server Standard is limited to 2Gb.
Windows 2003 system requirements:
http://www.microsoft.com/windowsserver2003/evaluation/sysreqs/default.mspx
How to configure memory for more than 2 GB in SQL Server:
http://support.microsoft.com/default.aspx?scid=kb;en-us;274750
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Reinhold" <reinholderlacher@.msn.com> wrote in message
news:OrbtVcisFHA.3424@.TK2MSFTNGP14.phx.gbl...
> Hi,
> I want to use MSSQL2000 on a server with 8GB ram amount.
> Is there a way to use this ram under Win2003 Server?
> What version of MSSQL2000 do I have to use?
> thx
> reinhold
>
I want to use MSSQL2000 on a server with 8GB ram amount.
Is there a way to use this ram under Win2003 Server?
What version of MSSQL2000 do I have to use?
thx
reinholdHi
You need to use:
Windows 2003 Enterprise Edition
SQL Server 2000 Enterprise Edition
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Reinhold" wrote:
> Hi,
> I want to use MSSQL2000 on a server with 8GB ram amount.
> Is there a way to use this ram under Win2003 Server?
> What version of MSSQL2000 do I have to use?
> thx
> reinhold
>
>|||See if this helps:
http://support.microsoft.com/default.aspx?scid=kb;en-us;274750&sd=tech
--
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Reinhold" <reinholderlacher@.msn.com> wrote in message
news:OrbtVcisFHA.3424@.TK2MSFTNGP14.phx.gbl...
Hi,
I want to use MSSQL2000 on a server with 8GB ram amount.
Is there a way to use this ram under Win2003 Server?
What version of MSSQL2000 do I have to use?
thx
reinhold|||> I want to use MSSQL2000 on a server with 8GB ram amount.
> Is there a way to use this ram under Win2003 Server?
Assuming 32-bit, you need Windows 2003 Server Enterprise Edition and SQL
Server Enterprise Edition. SQL Server AWE needs to be enabled to address
over 3GB. Windows 2003 Standard has a 4GB max memory limitation and SQL
Server Standard is limited to 2Gb.
Windows 2003 system requirements:
http://www.microsoft.com/windowsserver2003/evaluation/sysreqs/default.mspx
How to configure memory for more than 2 GB in SQL Server:
http://support.microsoft.com/default.aspx?scid=kb;en-us;274750
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Reinhold" <reinholderlacher@.msn.com> wrote in message
news:OrbtVcisFHA.3424@.TK2MSFTNGP14.phx.gbl...
> Hi,
> I want to use MSSQL2000 on a server with 8GB ram amount.
> Is there a way to use this ram under Win2003 Server?
> What version of MSSQL2000 do I have to use?
> thx
> reinhold
>
MSSQL2000 jdbc driver on UNIX ...
Hi experts,
I am new in java programming. I am wana to develop an application program
which can access MSSQL2000 under UNIX platform. I downloaded the jdbc
drivers for MSSQL2000 on Microsoft download center (Windows version & UNIX
version). I installed and set up on my machines,Windows 98 and
HPUX,respectively. And then, I do a sample code and try to accesss
MSSQL2000. It is works on Windows platform. But unfortunately, it does work
very well on my UNIX machine, and have an exception as
"com.microsoft.jdbc.sqlserver.SQLServerDriver".(co mplie pass). I have been
trying many times and can not get rid of this problem. Anyone can give me an
idea to solve it ? Thank you.
F.Y.I:
OS : HPUX10.20
JDK : 1.1.8
The configurlation in .cshrc :
...
set mypath = ( ... )
set hp93kpath = ( ... )
set javapath = ( ... )
set path = ($mypath $hp93kpath $javapath)
setenv classpath
install_dir/lib/msbase.jar:install_dir/lib/msutil.jar:install_dir/lib/mssqls
erver.jar
My sample code ..
import java.io.*;
import java.sql.*;
public class TestDB{
public static void main(String[] args){
try{
String mySQL = "select * from ABC";
Class.forname("com.microsoft.jdbc.sqlserver.SQLSer verDriver");
Connection cn =
DrvierManager.getConnection("jdbc:microsoft:sqlser ver://server_name:1433:Dat
abaseName = AAA","guest","guest");
Statement st = cn.createStatement();
resultSet rs = st.executeQuery(mySQL);
:
:
}catch(Exception e){
}finally{
rs.close();
st.clsoe();
cn.close();
}
}
}
Possibly a classpath problem. Do you see the jar's when you do:
shall> set | grep CLASSPATH
Or you could set the jar-CLASSPATH temporarely when you compile and run with
the 'env' shell statement, or on the javac/java command line.
Lars-Inge Tnnessen
www.larsinge.com
I am new in java programming. I am wana to develop an application program
which can access MSSQL2000 under UNIX platform. I downloaded the jdbc
drivers for MSSQL2000 on Microsoft download center (Windows version & UNIX
version). I installed and set up on my machines,Windows 98 and
HPUX,respectively. And then, I do a sample code and try to accesss
MSSQL2000. It is works on Windows platform. But unfortunately, it does work
very well on my UNIX machine, and have an exception as
"com.microsoft.jdbc.sqlserver.SQLServerDriver".(co mplie pass). I have been
trying many times and can not get rid of this problem. Anyone can give me an
idea to solve it ? Thank you.
F.Y.I:
OS : HPUX10.20
JDK : 1.1.8
The configurlation in .cshrc :
...
set mypath = ( ... )
set hp93kpath = ( ... )
set javapath = ( ... )
set path = ($mypath $hp93kpath $javapath)
setenv classpath
install_dir/lib/msbase.jar:install_dir/lib/msutil.jar:install_dir/lib/mssqls
erver.jar
My sample code ..
import java.io.*;
import java.sql.*;
public class TestDB{
public static void main(String[] args){
try{
String mySQL = "select * from ABC";
Class.forname("com.microsoft.jdbc.sqlserver.SQLSer verDriver");
Connection cn =
DrvierManager.getConnection("jdbc:microsoft:sqlser ver://server_name:1433:Dat
abaseName = AAA","guest","guest");
Statement st = cn.createStatement();
resultSet rs = st.executeQuery(mySQL);
:
:
}catch(Exception e){
}finally{
rs.close();
st.clsoe();
cn.close();
}
}
}
Possibly a classpath problem. Do you see the jar's when you do:
shall> set | grep CLASSPATH
Or you could set the jar-CLASSPATH temporarely when you compile and run with
the 'env' shell statement, or on the javac/java command line.
Lars-Inge Tnnessen
www.larsinge.com
MSSQL2000 Client Unable to create new table
HELP!
I'm new to SQL Server and I'm sure this is a simple problem.
But I can't seem to solve it.
Here's the problem:
My website & MS SQL 2000 Server are being hosted by Networksolutions.
Thru the Client Enterprise Manager I am Unable to create a New Table.
This is the error message I get:
" [MS Design Tools]-ODBC error: [Microsoft] [ODBC SQL SERVER DRIVER] [SQL SERVER] SELECT permission denied on object 'sysobjects', database 'namedb', owner'db' " :confused:Someone must grant you the necessary permissions for the database.
You're not authorized to create objects, simply.|||Thank you for your insieght.
I'm sure your are correct.
I'm new to SQL Server and I'm sure this is a simple problem.
But I can't seem to solve it.
Here's the problem:
My website & MS SQL 2000 Server are being hosted by Networksolutions.
Thru the Client Enterprise Manager I am Unable to create a New Table.
This is the error message I get:
" [MS Design Tools]-ODBC error: [Microsoft] [ODBC SQL SERVER DRIVER] [SQL SERVER] SELECT permission denied on object 'sysobjects', database 'namedb', owner'db' " :confused:Someone must grant you the necessary permissions for the database.
You're not authorized to create objects, simply.|||Thank you for your insieght.
I'm sure your are correct.
mssql2000 and oracle 10g on same server
I have mssql2000 running on a Windows 2003 server and now have a requirement to run an Oracle 10g database as well. Is it possible to run both mssql2000 and oracle 10g on the same server without running into any conflicts or will the two programs cause errors with each other?
Anyone have any experience with this? Oracle says it's technically possible but the tech had never seen it done.
ScottAlthough I've never run them in production, they run well enough on a test/dev machine. I'm pretty sure that you ought to be fine.
-PatP|||Thanks for the reply. We are a small business and I dont have a testbox to play with. I'll make sure everything gets backed up before install of course just to make sure.|||I'm just being nosy now, but those are the database engine equivalent of oxen. Either one of them is massive overkill for a small business... either one can handle the needs of a small business in their sleep.
Why do you need both of them? Software that is database engine specific?
To clarify on my previous post, I haven't run both SQL Server and Oracle 10g on one machine in production, but the two coexist happily on dev/test boxes.
One thing that I'd very strongly encourage is that you take whatever machine you can spare (whimpy is good in this case) and make it a dev/test box. You really don't want to be trying things out for the very first time on your production machine if you have any choice in the matter. I have actually seen people (more than one) lose their business by making that mistake.
-PatP|||I agree, it is a risky proposition. I will be making an image of the machine and backing up all data before doing the install. I also have to have it operational by tommorow because of business requirements. No pressure!
As to why we are running both you nailed it on the head. Software requirements. We will eventually, a couple years, be migrated completely to Oracle......or at least that's the plan today.
Anyone have any experience with this? Oracle says it's technically possible but the tech had never seen it done.
ScottAlthough I've never run them in production, they run well enough on a test/dev machine. I'm pretty sure that you ought to be fine.
-PatP|||Thanks for the reply. We are a small business and I dont have a testbox to play with. I'll make sure everything gets backed up before install of course just to make sure.|||I'm just being nosy now, but those are the database engine equivalent of oxen. Either one of them is massive overkill for a small business... either one can handle the needs of a small business in their sleep.
Why do you need both of them? Software that is database engine specific?
To clarify on my previous post, I haven't run both SQL Server and Oracle 10g on one machine in production, but the two coexist happily on dev/test boxes.
One thing that I'd very strongly encourage is that you take whatever machine you can spare (whimpy is good in this case) and make it a dev/test box. You really don't want to be trying things out for the very first time on your production machine if you have any choice in the matter. I have actually seen people (more than one) lose their business by making that mistake.
-PatP|||I agree, it is a risky proposition. I will be making an image of the machine and backing up all data before doing the install. I also have to have it operational by tommorow because of business requirements. No pressure!
As to why we are running both you nailed it on the head. Software requirements. We will eventually, a couple years, be migrated completely to Oracle......or at least that's the plan today.
Mssql2000
Environment: OS-Win2K MSSQL2000
My problem:
I need to insert data from a table in MSSQL2000 to a Sybase V12.5 table.
I did a C++ program (as extended stored procedure-ESP), which runs O.K. if I start it manually.
If I start it thru a MSSQL2000 Job (defining a job, inside it is a SP and inside of it is my start of ESP), then I'm getting some errors.
This is now priority 2.
Priority 1 is:
for testing of this ESP I have to stop MSSQLSERVER service and copy the new version if ESP. And then I'm starting MSSQLSERVER service and SQLSERVERAGENT. Both are running O.K. without any events in Event Viewer.
But if I'd like to start SQL Query Analyzer I can't login into it. I'm getting an error:
Unable to connect to server:Msg 17, Level 16, State 1
[Microsoft][ODBC SQL Server Driver][TCP/IP Socekts] SQL Server does not exist or access denied"
Below are 2 files: ERRRLOG and SQLAGENT.OUT
************************************************** *********************************************
ERRORLOG
************************************************** *********************************************
2003-05-29 08:26:18.22 server Microsoft SQL Server 2000 - 8.00.194 (Intel X86)
Aug 6 2000 00:57:48
Copyright (c) 1988-2000 Microsoft Corporation
Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 3)
2003-05-29 08:26:18.32 server Copyright (C) 1988-2000 Microsoft Corporation.
2003-05-29 08:26:18.32 server All rights reserved.
2003-05-29 08:26:18.32 server Server Process ID is 828.
2003-05-29 08:26:18.32 server Logging SQL Server messages in file 'c:\MSSQL\log\ERRORLOG'.
2003-05-29 08:26:18.48 server SQL Server is starting at priority class 'normal'(1 CPU detected).
2003-05-29 08:26:19.60 server SQL Server configured for thread mode processing.
2003-05-29 08:26:19.74 server Using dynamic lock allocation. [2500] Lock Blocks, [5000] Lock Owner Blocks.
2003-05-29 08:26:19.79 server Attempting to initialize Distributed Transaction Coordinator.
2003-05-29 08:26:22.69 server Failed to obtain TransactionDispenserInterface: Result Code = 0x80004005
2003-05-29 08:26:23.16 spid3 Starting up database 'master'.
2003-05-29 08:26:27.17 server Using 'SSNETLIB.DLL' version '8.0.194'.
2003-05-29 08:26:27.17 spid5 Starting up database 'model'.
2003-05-29 08:26:27.27 spid3 Server name is 'OTCPSRV01'.
2003-05-29 08:26:27.31 spid8 Starting up database 'msdb'.
2003-05-29 08:26:27.31 spid9 Starting up database 'pubs'.
2003-05-29 08:26:27.31 spid10 Starting up database 'QA'.
2003-05-29 08:26:27.31 spid11 Starting up database 'DEVEXEC'.
2003-05-29 08:26:29.55 spid5 Clearing tempdb database.
2003-05-29 08:26:29.89 spid11 Analysis of database 'DEVEXEC' (7) is 100% complete (approximately 0 more seconds)
2003-05-29 08:26:31.21 spid10 Analysis of database 'QA' (6) is 100% complete (approximately 0 more seconds)
2003-05-29 08:26:34.20 server SQL server listening on Shared Memory.
2003-05-29 08:26:34.20 server SQL Server is ready for client connections
2003-05-29 08:26:37.49 spid5 Starting up database 'tempdb'.
2003-05-29 08:26:38.64 spid5 Analysis of database 'tempdb' (2) is 100% complete (approximately 0 more seconds)
2003-05-29 08:26:39.87 spid3 Recovery complete.
2003-05-29 08:26:58.87 spid51 Using 'xpsqlbot.dll' version '2000.80.194' to execute extended stored procedure 'xp_qv'.
2003-05-29 08:28:03.56 spid53 Using 'xplog70.dll' version '2000.80.194' to execute extended stored procedure 'xp_cmdshell'.
2003-05-29 08:28:05.23 spid53 Using 'xpstar.dll' version '2000.80.194' to execute extended stored procedure 'xp_sqlagent_enum_jobs'.
************************************************** *********************************************
SQLAGENT.OUT
************************************************** *********************************************
2003-05-29 08:26:59 - ? [100] Microsoft SQLServerAgent version 8.00.194 (x86 unicode retail build) : Process ID 1284
2003-05-29 08:26:59 - ? [101] SQL Server OTCPSRV01 version 8.00.194 (0 connection limit)
2003-05-29 08:26:59 - ? [102] SQL Server ODBC driver version 3.80.528
2003-05-29 08:26:59 - ? [103] NetLib being used by driver is DBMSSHRN.DLL; Local host server is (local)
2003-05-29 08:26:59 - ? [310] 1 processor(s) and 768 MB RAM detected
2003-05-29 08:26:59 - ? [339] Local computer is OTCPSRV01 running Windows NT 5.0 (2195) Service Pack 3
2003-05-29 08:27:02 - ? [129] SQLSERVERAGENT starting under Windows NT service control
2003-05-29 08:27:02 - + [260] Unable to start mail session (reason: No mail profile defined)
2003-05-29 08:27:02 - + [396] An idle CPU condition has not been defined - OnIdle job schedules will have no effect
2003-05-29 08:28:33 - ! [298] SQLServer Error: 17, SQL Server does not exist or access denied. [SQLSTATE 08001]
2003-05-29 08:28:33 - ! [298] SQLServer Error: 10061, ConnectionOpen (Connect()). [SQLSTATE 01000]
2003-05-29 08:28:33 - ! [382] Logon to server 'OTCPSRV01' failed (ConnAttemptCachableOp)
2003-05-29 08:28:33 - ! [298] SQLServer Error: 17, SQL Server does not exist or access denied. [SQLSTATE 08001]
2003-05-29 08:28:33 - ! [298] SQLServer Error: 10061, ConnectionOpen (Connect()). [SQLSTATE 01000]
2003-05-29 08:28:33 - ! [382] Logon to server 'OTCPSRV01' failed (ConnAttemptCachableOp)
the last 3 lines are repeating ....
The definition of Client Network Utility is O.K. ( it was good until I have started with tests)
SSNETLIB.DLL is V2000.80.194 - is it O.K. or too old for this task?
My question is - what should I do? to make SQL runable?:(May take help of this KBA (http://support.microsoft.com/default.aspx?scid=kb;en-us;Q311836&gssnb=1).|||Originally posted by Satya
May take help of this KBA (http://support.microsoft.com/default.aspx?scid=kb;en-us;Q311836&gssnb=1).
Thank you for your advice. I'll check it just now!:rolleyes: :rolleyes:|||Originally posted by Wedlechowicz
Thank you for your advice. I'll check it just now!:rolleyes: :rolleyes:
Hi Satya,
I have checked it all.
Sorry, but it doesn't work.
And it's funny, but I have set in Services the MSSQLSERV on MANUAL and after reboot that services is started!!! Why? I thought it won't be started after reboot. And there's no Job in MSSQL that could do it automatically.
What do you mean about it all?
Zbig:confused:|||Make sure to make the SQLAgent service manual too.
Start your SQL server service first and then agent service, see what error you will get. Seems your SQL server service is not started correctly. Make sure your agent service is set up correctly including the username and password.|||True, make sure to have necessary privileges for SQL services account.|||Originally posted by Satya
True, make sure to have necessary privileges for SQL services account.
Hi,
I decided to do so:
I reinstalled the whole MSSQL Server, e.g. thru it I have got the "NEW" refreshed Registry (ONLY this and nothing MORE) and all was then O.K.
Thank you for this help!
:) :p
My problem:
I need to insert data from a table in MSSQL2000 to a Sybase V12.5 table.
I did a C++ program (as extended stored procedure-ESP), which runs O.K. if I start it manually.
If I start it thru a MSSQL2000 Job (defining a job, inside it is a SP and inside of it is my start of ESP), then I'm getting some errors.
This is now priority 2.
Priority 1 is:
for testing of this ESP I have to stop MSSQLSERVER service and copy the new version if ESP. And then I'm starting MSSQLSERVER service and SQLSERVERAGENT. Both are running O.K. without any events in Event Viewer.
But if I'd like to start SQL Query Analyzer I can't login into it. I'm getting an error:
Unable to connect to server:Msg 17, Level 16, State 1
[Microsoft][ODBC SQL Server Driver][TCP/IP Socekts] SQL Server does not exist or access denied"
Below are 2 files: ERRRLOG and SQLAGENT.OUT
************************************************** *********************************************
ERRORLOG
************************************************** *********************************************
2003-05-29 08:26:18.22 server Microsoft SQL Server 2000 - 8.00.194 (Intel X86)
Aug 6 2000 00:57:48
Copyright (c) 1988-2000 Microsoft Corporation
Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 3)
2003-05-29 08:26:18.32 server Copyright (C) 1988-2000 Microsoft Corporation.
2003-05-29 08:26:18.32 server All rights reserved.
2003-05-29 08:26:18.32 server Server Process ID is 828.
2003-05-29 08:26:18.32 server Logging SQL Server messages in file 'c:\MSSQL\log\ERRORLOG'.
2003-05-29 08:26:18.48 server SQL Server is starting at priority class 'normal'(1 CPU detected).
2003-05-29 08:26:19.60 server SQL Server configured for thread mode processing.
2003-05-29 08:26:19.74 server Using dynamic lock allocation. [2500] Lock Blocks, [5000] Lock Owner Blocks.
2003-05-29 08:26:19.79 server Attempting to initialize Distributed Transaction Coordinator.
2003-05-29 08:26:22.69 server Failed to obtain TransactionDispenserInterface: Result Code = 0x80004005
2003-05-29 08:26:23.16 spid3 Starting up database 'master'.
2003-05-29 08:26:27.17 server Using 'SSNETLIB.DLL' version '8.0.194'.
2003-05-29 08:26:27.17 spid5 Starting up database 'model'.
2003-05-29 08:26:27.27 spid3 Server name is 'OTCPSRV01'.
2003-05-29 08:26:27.31 spid8 Starting up database 'msdb'.
2003-05-29 08:26:27.31 spid9 Starting up database 'pubs'.
2003-05-29 08:26:27.31 spid10 Starting up database 'QA'.
2003-05-29 08:26:27.31 spid11 Starting up database 'DEVEXEC'.
2003-05-29 08:26:29.55 spid5 Clearing tempdb database.
2003-05-29 08:26:29.89 spid11 Analysis of database 'DEVEXEC' (7) is 100% complete (approximately 0 more seconds)
2003-05-29 08:26:31.21 spid10 Analysis of database 'QA' (6) is 100% complete (approximately 0 more seconds)
2003-05-29 08:26:34.20 server SQL server listening on Shared Memory.
2003-05-29 08:26:34.20 server SQL Server is ready for client connections
2003-05-29 08:26:37.49 spid5 Starting up database 'tempdb'.
2003-05-29 08:26:38.64 spid5 Analysis of database 'tempdb' (2) is 100% complete (approximately 0 more seconds)
2003-05-29 08:26:39.87 spid3 Recovery complete.
2003-05-29 08:26:58.87 spid51 Using 'xpsqlbot.dll' version '2000.80.194' to execute extended stored procedure 'xp_qv'.
2003-05-29 08:28:03.56 spid53 Using 'xplog70.dll' version '2000.80.194' to execute extended stored procedure 'xp_cmdshell'.
2003-05-29 08:28:05.23 spid53 Using 'xpstar.dll' version '2000.80.194' to execute extended stored procedure 'xp_sqlagent_enum_jobs'.
************************************************** *********************************************
SQLAGENT.OUT
************************************************** *********************************************
2003-05-29 08:26:59 - ? [100] Microsoft SQLServerAgent version 8.00.194 (x86 unicode retail build) : Process ID 1284
2003-05-29 08:26:59 - ? [101] SQL Server OTCPSRV01 version 8.00.194 (0 connection limit)
2003-05-29 08:26:59 - ? [102] SQL Server ODBC driver version 3.80.528
2003-05-29 08:26:59 - ? [103] NetLib being used by driver is DBMSSHRN.DLL; Local host server is (local)
2003-05-29 08:26:59 - ? [310] 1 processor(s) and 768 MB RAM detected
2003-05-29 08:26:59 - ? [339] Local computer is OTCPSRV01 running Windows NT 5.0 (2195) Service Pack 3
2003-05-29 08:27:02 - ? [129] SQLSERVERAGENT starting under Windows NT service control
2003-05-29 08:27:02 - + [260] Unable to start mail session (reason: No mail profile defined)
2003-05-29 08:27:02 - + [396] An idle CPU condition has not been defined - OnIdle job schedules will have no effect
2003-05-29 08:28:33 - ! [298] SQLServer Error: 17, SQL Server does not exist or access denied. [SQLSTATE 08001]
2003-05-29 08:28:33 - ! [298] SQLServer Error: 10061, ConnectionOpen (Connect()). [SQLSTATE 01000]
2003-05-29 08:28:33 - ! [382] Logon to server 'OTCPSRV01' failed (ConnAttemptCachableOp)
2003-05-29 08:28:33 - ! [298] SQLServer Error: 17, SQL Server does not exist or access denied. [SQLSTATE 08001]
2003-05-29 08:28:33 - ! [298] SQLServer Error: 10061, ConnectionOpen (Connect()). [SQLSTATE 01000]
2003-05-29 08:28:33 - ! [382] Logon to server 'OTCPSRV01' failed (ConnAttemptCachableOp)
the last 3 lines are repeating ....
The definition of Client Network Utility is O.K. ( it was good until I have started with tests)
SSNETLIB.DLL is V2000.80.194 - is it O.K. or too old for this task?
My question is - what should I do? to make SQL runable?:(May take help of this KBA (http://support.microsoft.com/default.aspx?scid=kb;en-us;Q311836&gssnb=1).|||Originally posted by Satya
May take help of this KBA (http://support.microsoft.com/default.aspx?scid=kb;en-us;Q311836&gssnb=1).
Thank you for your advice. I'll check it just now!:rolleyes: :rolleyes:|||Originally posted by Wedlechowicz
Thank you for your advice. I'll check it just now!:rolleyes: :rolleyes:
Hi Satya,
I have checked it all.
Sorry, but it doesn't work.
And it's funny, but I have set in Services the MSSQLSERV on MANUAL and after reboot that services is started!!! Why? I thought it won't be started after reboot. And there's no Job in MSSQL that could do it automatically.
What do you mean about it all?
Zbig:confused:|||Make sure to make the SQLAgent service manual too.
Start your SQL server service first and then agent service, see what error you will get. Seems your SQL server service is not started correctly. Make sure your agent service is set up correctly including the username and password.|||True, make sure to have necessary privileges for SQL services account.|||Originally posted by Satya
True, make sure to have necessary privileges for SQL services account.
Hi,
I decided to do so:
I reinstalled the whole MSSQL Server, e.g. thru it I have got the "NEW" refreshed Registry (ONLY this and nothing MORE) and all was then O.K.
Thank you for this help!
:) :p
mssql2000
Hi
I am changing my server from mssq7 to sql2000
Do i need to upgrade my mssql7 databse to 2000.
or only i want to just attach db to 2000 server.
thanks.
Thanks
You can attach a 7 database to 2000. Another option is backup and restore. Just make sure you test
your applications...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"shif" <ns_0001@.hotmail.com> wrote in message
news:214DE35F-B234-4519-8754-E7D14B317A91@.microsoft.com...
> Hi
> I am changing my server from mssq7 to sql2000
> Do i need to upgrade my mssql7 databse to 2000.
> or only i want to just attach db to 2000 server.
> thanks.
> --
> Thanks
I am changing my server from mssq7 to sql2000
Do i need to upgrade my mssql7 databse to 2000.
or only i want to just attach db to 2000 server.
thanks.
Thanks
You can attach a 7 database to 2000. Another option is backup and restore. Just make sure you test
your applications...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"shif" <ns_0001@.hotmail.com> wrote in message
news:214DE35F-B234-4519-8754-E7D14B317A91@.microsoft.com...
> Hi
> I am changing my server from mssq7 to sql2000
> Do i need to upgrade my mssql7 databse to 2000.
> or only i want to just attach db to 2000 server.
> thanks.
> --
> Thanks
mssql2000
Hi
I am changing my server from mssq7 to sql2000
Do i need to upgrade my mssql7 databse to 2000.
or only i want to just attach db to 2000 server.
thanks.
--
ThanksYou can attach a 7 database to 2000. Another option is backup and restore. J
ust make sure you test
your applications...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"shif" <ns_0001@.hotmail.com> wrote in message
news:214DE35F-B234-4519-8754-E7D14B317A91@.microsoft.com...
> Hi
> I am changing my server from mssq7 to sql2000
> Do i need to upgrade my mssql7 databse to 2000.
> or only i want to just attach db to 2000 server.
> thanks.
> --
> Thanks
I am changing my server from mssq7 to sql2000
Do i need to upgrade my mssql7 databse to 2000.
or only i want to just attach db to 2000 server.
thanks.
--
ThanksYou can attach a 7 database to 2000. Another option is backup and restore. J
ust make sure you test
your applications...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"shif" <ns_0001@.hotmail.com> wrote in message
news:214DE35F-B234-4519-8754-E7D14B317A91@.microsoft.com...
> Hi
> I am changing my server from mssq7 to sql2000
> Do i need to upgrade my mssql7 databse to 2000.
> or only i want to just attach db to 2000 server.
> thanks.
> --
> Thanks
mssql2000
Hi
I am changing my server from mssq7 to sql2000
Do i need to upgrade my mssql7 databse to 2000.
or only i want to just attach db to 2000 server.
thanks.
--
ThanksYou can attach a 7 database to 2000. Another option is backup and restore. Just make sure you test
your applications...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"shif" <ns_0001@.hotmail.com> wrote in message
news:214DE35F-B234-4519-8754-E7D14B317A91@.microsoft.com...
> Hi
> I am changing my server from mssq7 to sql2000
> Do i need to upgrade my mssql7 databse to 2000.
> or only i want to just attach db to 2000 server.
> thanks.
> --
> Thanks
I am changing my server from mssq7 to sql2000
Do i need to upgrade my mssql7 databse to 2000.
or only i want to just attach db to 2000 server.
thanks.
--
ThanksYou can attach a 7 database to 2000. Another option is backup and restore. Just make sure you test
your applications...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"shif" <ns_0001@.hotmail.com> wrote in message
news:214DE35F-B234-4519-8754-E7D14B317A91@.microsoft.com...
> Hi
> I am changing my server from mssq7 to sql2000
> Do i need to upgrade my mssql7 databse to 2000.
> or only i want to just attach db to 2000 server.
> thanks.
> --
> Thanks
Subscribe to:
Posts (Atom)