Comparing DBs

is there any utility or program available that will compare two versions of
the same SQL Server database in terms of definition and objects. I don't
want to compare data. I need to see the differences in tables columns views
etc.
Thanks,
GaryThere are quite a few companies that make such products. Check out this
list: http://vyaskn.tripod.com/thirdparty.htm
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"Gary" <gb@.nospam.com> wrote in message
news:ewGG5cf2DHA.2308@.TK2MSFTNGP11.phx.gbl...
is there any utility or program available that will compare two versions of
the same SQL Server database in terms of definition and objects. I don't
want to compare data. I need to see the differences in tables columns views
etc.
Thanks,
Gary|||We use the following tool
http://www.adeptsql.com/
Its cheap, very accurate, very fast and will also update
your out of sync database if you wish. There is also a
trial version which you can download.
J
>--Original Message--
>is there any utility or program available that will
compare two versions of
>the same SQL Server database in terms of definition and
objects. I don't
>want to compare data. I need to see the differences in
tables columns views
>etc.
>Thanks,
>Gary
>
>.
>|||We use ERWin by Computer Associates.
a bit spendy but it does More then just compare Databases.
http://www3.ca.com/Solutions/Product.asp?ID=260
Gregory A Jackson
PDX, Oregon|||Hi Gary,
Thank you for using MSDN Newsgroup! It's my pleasure to assist you with
your issue.
For your question of compare the two versions of the same SQL Server
database in terms of definitions and objects but not data in them. Besides
the utiltities suggested by our MVPs and community members, if the compare
is quite simple, you can just generate a 'script' that define the objects
in 2 SQL Server respectively and compare the script. To generate the
script, they can use SQL Enterprise Manager and choose the "Object|Generate
SQL Script..." menu item. Another way is to use 'sp_help' upon each object
in the 2 database and compare them.
Hope this helps. If you still have questions on this issue, please feel
free to post new message here and I am ready to help!
Best regards
Baisong Wei
Microsoft Online Support
----
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.|||Hi Gary,
As said in the answers, you can use tools to compare the databases.
I prefer to use the sysobjects table to do that, simply by doing
a
SELECT * from db1.sysobjects where not in (SELECT * from db2.sysobjects)
or
SELECT * from db2.sysobjects where not in (SELECT * from db1.sysobjects)
This works if you want to analyse the difference in term of tables
and fields.
To have a deeper analysis (fields of different types) it is more difficult
but possible with other system tables like syscolumns.
Gilles
"Gary" <gb@.nospam.com> wrote in message news:<ewGG5cf2DHA.2308@.TK2MSFTNGP11.phx.gbl>...
> is there any utility or program available that will compare two versions of
> the same SQL Server database in terms of definition and objects. I don't
> want to compare data. I need to see the differences in tables columns views
> etc.
> Thanks,
> Gary|||also check out DB Ghost @. www.dbghost.com
regards,
Mark Baekdal
>--Original Message--
>is there any utility or program available that will
compare two versions of
>the same SQL Server database in terms of definition and
objects. I don't
>want to compare data. I need to see the differences in
tables columns views
>etc.
>Thanks,
>Gary
>
>.
>|||I downloaded it and tried it out. Works great. Many thanks.
Gary
"Julie" <anonymous@.discussions.microsoft.com> wrote in message
news:0d0601c3d9fa$103b29b0$a601280a@.phx.gbl...
> We use the following tool
> http://www.adeptsql.com/
> Its cheap, very accurate, very fast and will also update
> your out of sync database if you wish. There is also a
> trial version which you can download.
> J
>
> >--Original Message--
> >is there any utility or program available that will
> compare two versions of
> >the same SQL Server database in terms of definition and
> objects. I don't
> >want to compare data. I need to see the differences in
> tables columns views
> >etc.
> >Thanks,
> >Gary
> >
> >
> >.
> >

Comparing DBs

is there any utility or program available that will compare two versions of
the same SQL Server database in terms of definition and objects. I don't
want to compare data. I need to see the differences in tables columns views
etc.
Thanks,
GaryThere are quite a few companies that make such products. Check out this
list: http://vyaskn.tripod.com/thirdparty.htm
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"Gary" <gb@.nospam.com> wrote in message
news:ewGG5cf2DHA.2308@.TK2MSFTNGP11.phx.gbl...
is there any utility or program available that will compare two versions of
the same SQL Server database in terms of definition and objects. I don't
want to compare data. I need to see the differences in tables columns views
etc.
Thanks,
Gary|||We use ERWin by Computer Associates.
a bit spendy but it does More then just compare Databases.
http://www3.ca.com/Solutions/Product.asp?ID=260
Gregory A Jackson
PDX, Oregon|||Hi Gary,
Thank you for using MSDN Newsgroup! It's my pleasure to assist you with
your issue.
For your question of compare the two versions of the same SQL Server
database in terms of definitions and objects but not data in them. Besides
the utiltities suggested by our MVPs and community members, if the compare
is quite simple, you can just generate a 'script' that define the objects
in 2 SQL Server respectively and compare the script. To generate the
script, they can use SQL Enterprise Manager and choose the "Object|Generate
SQL Script..." menu item. Another way is to use 'sp_help' upon each object
in the 2 database and compare them.
Hope this helps. If you still have questions on this issue, please feel
free to post new message here and I am ready to help!
Best regards
Baisong Wei
Microsoft Online Support
----
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.|||Hi Gary,
As said in the answers, you can use tools to compare the databases.
I prefer to use the sysobjects table to do that, simply by doing
a
SELECT * from db1.sysobjects where not in (SELECT * from db2.sysobjects)
or
SELECT * from db2.sysobjects where not in (SELECT * from db1.sysobjects)
This works if you want to analyse the difference in term of tables
and fields.
To have a deeper analysis (fields of different types) it is more difficult
but possible with other system tables like syscolumns.
Gilles
"Gary" <gb@.nospam.com> wrote in message news:<ewGG5cf2DHA.2308@.TK2MSFTNGP11.phx.gbl>...

quote:

---

[col
or=darkred]
> is there any utility or program available that will compare two versions o
f
> the same SQL Server database in terms of definition and objects. I don't
> want to compare data. I need to see the differences in tables columns vie
ws
> etc.
> Thanks,
> Gary[/color]

---

sqlsql

Communciation between MS SQL Server and client

I'm trying to understand the client and server communication. But I have run into some terms which I need some help to understand:
1. Named Pipes over NetBIOS
2. Named Pipes over NetBEUI
3. Named Pipes over TCP/IP
4. NetBIOS over TCP/IP
5. SMB over NetBios
6. SMB over NetBEUI
7. SMB over TCP/IP
8. RPC over NetBIOS
9. RPC over NetBEUI
10. RPC over TCP/IP
I have a feeling that #1 and #5 actually means the same thing. Also, #3 and #7 means the same thing.
Is the following the correct order of the communication path?
Named Pipes
SMB
NetBIOS
TCP/IP or NetBEUI
I have the following understanding:
1. Named Pipes is a network library.
2. TCP/IP and NetBEUI are network transport protocols.
You have many things mixed together that are fundamentally different.
This can't easily be explained. I think your point is which ports must
be enabled based on what services are being used, as opposed to just
being active and unused. This is difficult to answer without alot of
experimentation and understanding of the interdependance of services.
I understood named pipes to be an app to app info exchange by files.
Named pipes can operate over TCP/IP, but are verbose and performance
becomes degraded over slow networks.
RPC stands for remote procedure call. These are transmitted over
TCP/IP RPC are means by whihc applications communicate and are at
least a level above TCP/IP..
SMB is also referred to as Samba - means of Windows and Linux file
sharing, and is again at a higher level than TCP/IP.
NetBios is a protocol that I understood was native to Novel networks,
and not TCP/IP, but apparanetly one can use NetBios over TCP/IP.
On Tue, 29 Jun 2004 13:03:02 -0700, "=?Utf-8?B?cGV0ZXI=?="
<peter@.discussions.microsoft.com> wrote:

>I'm trying to understand the client and server communication. But I have run into some terms which I need some help to understand:
>1. Named Pipes over NetBIOS
>2. Named Pipes over NetBEUI
>3. Named Pipes over TCP/IP
>4. NetBIOS over TCP/IP
>5. SMB over NetBios
>6. SMB over NetBEUI
>7. SMB over TCP/IP
>8. RPC over NetBIOS
>9. RPC over NetBEUI
>10. RPC over TCP/IP
>I have a feeling that #1 and #5 actually means the same thing. Also, #3 and #7 means the same thing.
>Is the following the correct order of the communication path?
>Named Pipes
>SMB
>NetBIOS
>TCP/IP or NetBEUI
>I have the following understanding:
>1. Named Pipes is a network library.
>2. TCP/IP and NetBEUI are network transport protocols.
>
|||Hi Lou,
Thank you for the explanation.
Are the followings correct?
1. #1 Named Pipes over NetBIOS already includes #5 SMB over NetBios.
2. #2 Named Pipes over NetBEUI already includes #1 Named Pipes over NetBIOS, #5 SMB over NetBios, and #6 SMB over NetBEUI.
3. #3 Named Pipes over TCP/IP already includes #4 NetBIOS over TCP/IP, #5 SMB over NetBios, and #7 SMB over TCP/IP.
Thank you for your help,
Peter
"Lou Arnold" wrote:

> You have many things mixed together that are fundamentally different.
> This can't easily be explained. I think your point is which ports must
> be enabled based on what services are being used, as opposed to just
> being active and unused. This is difficult to answer without alot of
> experimentation and understanding of the interdependance of services.
> I understood named pipes to be an app to app info exchange by files.
> Named pipes can operate over TCP/IP, but are verbose and performance
> becomes degraded over slow networks.
> RPC stands for remote procedure call. These are transmitted over
> TCP/IP RPC are means by whihc applications communicate and are at
> least a level above TCP/IP..
> SMB is also referred to as Samba - means of Windows and Linux file
> sharing, and is again at a higher level than TCP/IP.
> NetBios is a protocol that I understood was native to Novel networks,
> and not TCP/IP, but apparanetly one can use NetBios over TCP/IP.
> On Tue, 29 Jun 2004 13:03:02 -0700, "=?Utf-8?B?cGV0ZXI=?="
> <peter@.discussions.microsoft.com> wrote:
>
>
|||Sorry, i realy don't have enough experience to answer your questions
and I'm not sure anyone can in this forum. You'l need to browse the
internet or ask in networking groups.
On Wed, 30 Jun 2004 01:05:01 -0700, "=?Utf-8?B?UGV0ZXI=?="
<Peter@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Hi Lou,
>Thank you for the explanation.
>Are the followings correct?
>1. #1 Named Pipes over NetBIOS already includes #5 SMB over NetBios.
>2. #2 Named Pipes over NetBEUI already includes #1 Named Pipes over NetBIOS, #5 SMB over NetBios, and #6 SMB over NetBEUI.
>3. #3 Named Pipes over TCP/IP already includes #4 NetBIOS over TCP/IP, #5 SMB over NetBios, and #7 SMB over TCP/IP.
>Thank you for your help,
>Peter
>
>"Lou Arnold" wrote:
|||Lou,
Thank you for your help. I understand these questions are kind of beyond the scope of SQL Server.
Peter
"Lou Arnold" wrote:

> Sorry, i realy don't have enough experience to answer your questions
> and I'm not sure anyone can in this forum. You'l need to browse the
> internet or ask in networking groups.
>
> On Wed, 30 Jun 2004 01:05:01 -0700, "=?Utf-8?B?UGV0ZXI=?="
> <Peter@.discussions.microsoft.com> wrote:
>
>

Communciation between MS SQL Server and client

I'm trying to understand the client and server communication. But I have run
into some terms which I need some help to understand:
1. Named Pipes over NetBIOS
2. Named Pipes over NetBEUI
3. Named Pipes over TCP/IP
4. NetBIOS over TCP/IP
5. SMB over NetBios
6. SMB over NetBEUI
7. SMB over TCP/IP
8. RPC over NetBIOS
9. RPC over NetBEUI
10. RPC over TCP/IP
I have a feeling that #1 and #5 actually means the same thing. Also, #3 and
#7 means the same thing.
Is the following the correct order of the communication path?
Named Pipes
SMB
NetBIOS
TCP/IP or NetBEUI
I have the following understanding:
1. Named Pipes is a network library.
2. TCP/IP and NetBEUI are network transport protocols.You have many things mixed together that are fundamentally different.
This can't easily be explained. I think your point is which ports must
be enabled based on what services are being used, as opposed to just
being active and unused. This is difficult to answer without alot of
experimentation and understanding of the interdependance of services.
I understood named pipes to be an app to app info exchange by files.
Named pipes can operate over TCP/IP, but are verbose and performance
becomes degraded over slow networks.
RPC stands for remote procedure call. These are transmitted over
TCP/IP RPC are means by whihc applications communicate and are at
least a level above TCP/IP..
SMB is also referred to as Samba - means of Windows and Linux file
sharing, and is again at a higher level than TCP/IP.
NetBios is a protocol that I understood was native to Novel networks,
and not TCP/IP, but apparanetly one can use NetBios over TCP/IP.
On Tue, 29 Jun 2004 13:03:02 -0700, "examnotes"
<peter@.discussions.microsoft.com> wrote:

>I'm trying to understand the client and server communication. But I have ru
n into some terms which I need some help to understand:
>1. Named Pipes over NetBIOS
>2. Named Pipes over NetBEUI
>3. Named Pipes over TCP/IP
>4. NetBIOS over TCP/IP
>5. SMB over NetBios
>6. SMB over NetBEUI
>7. SMB over TCP/IP
>8. RPC over NetBIOS
>9. RPC over NetBEUI
>10. RPC over TCP/IP
>I have a feeling that #1 and #5 actually means the same thing. Also, #3 and
#7 means the same thing.
>Is the following the correct order of the communication path?
>Named Pipes
>SMB
>NetBIOS
>TCP/IP or NetBEUI
>I have the following understanding:
>1. Named Pipes is a network library.
>2. TCP/IP and NetBEUI are network transport protocols.
>|||Hi Lou,
Thank you for the explanation.
Are the followings correct?
1. #1 Named Pipes over NetBIOS already includes #5 SMB over NetBios.
2. #2 Named Pipes over NetBEUI already includes #1 Named Pipes over NetBIOS,
#5 SMB over NetBios, and #6 SMB over NetBEUI.
3. #3 Named Pipes over TCP/IP already includes #4 NetBIOS over TCP/IP, #5 SM
B over NetBios, and #7 SMB over TCP/IP.
Thank you for your help,
Peter
"Lou Arnold" wrote:

> You have many things mixed together that are fundamentally different.
> This can't easily be explained. I think your point is which ports must
> be enabled based on what services are being used, as opposed to just
> being active and unused. This is difficult to answer without alot of
> experimentation and understanding of the interdependance of services.
> I understood named pipes to be an app to app info exchange by files.
> Named pipes can operate over TCP/IP, but are verbose and performance
> becomes degraded over slow networks.
> RPC stands for remote procedure call. These are transmitted over
> TCP/IP RPC are means by whihc applications communicate and are at
> least a level above TCP/IP..
> SMB is also referred to as Samba - means of Windows and Linux file
> sharing, and is again at a higher level than TCP/IP.
> NetBios is a protocol that I understood was native to Novel networks,
> and not TCP/IP, but apparanetly one can use NetBios over TCP/IP.
> On Tue, 29 Jun 2004 13:03:02 -0700, "examnotes"
> <peter@.discussions.microsoft.com> wrote:
>
>|||Sorry, i realy don't have enough experience to answer your questions
and I'm not sure anyone can in this forum. You'l need to browse the
internet or ask in networking groups.
On Wed, 30 Jun 2004 01:05:01 -0700, "examnotes"
<Peter@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Hi Lou,
>Thank you for the explanation.
>Are the followings correct?
>1. #1 Named Pipes over NetBIOS already includes #5 SMB over NetBios.
>2. #2 Named Pipes over NetBEUI already includes #1 Named Pipes over NetBIOS
, #5 SMB over NetBios, and #6 SMB over NetBEUI.
>3. #3 Named Pipes over TCP/IP already includes #4 NetBIOS over TCP/IP, #5 S
MB over NetBios, and #7 SMB over TCP/IP.
>Thank you for your help,
>Peter
>
>"Lou Arnold" wrote:
>|||Lou,
Thank you for your help. I understand these questions are kind of beyond t
he scope of SQL Server.
Peter
"Lou Arnold" wrote:

> Sorry, i realy don't have enough experience to answer your questions
> and I'm not sure anyone can in this forum. You'l need to browse the
> internet or ask in networking groups.
>
> On Wed, 30 Jun 2004 01:05:01 -0700, "examnotes"
> <Peter@.discussions.microsoft.com> wrote:
>
>