Hi,
Sorry for the bad English.
I need a tool to see the difference between 2 databases.
Octavian:
SQLExecMS has this feature, Try http://www.laplas-soft.com/
Regards,
MartinH.
"Octavian RUSE" <oruse@.saratoga.ro> escribi en el mensaje
news:uZGTQkOQFHA.164@.TK2MSFTNGP12.phx.gbl...
> Hi,
> Sorry for the bad English.
> I need a tool to see the difference between 2 databases.
>
|||thanx
"Martin Hart - Memory Soft, S.L." <memorysoftsl _at_ infotelecom _dot_ es>
wrote in message news:Os2ConOQFHA.2876@.TK2MSFTNGP09.phx.gbl...
> Octavian:
> SQLExecMS has this feature, Try http://www.laplas-soft.com/
> Regards,
> MartinH.
> "Octavian RUSE" <oruse@.saratoga.ro> escribi en el mensaje
> news:uZGTQkOQFHA.164@.TK2MSFTNGP12.phx.gbl...
>
|||"Octavian RUSE" <oruse@.saratoga.ro> wrote in message
news:uZGTQkOQFHA.164@.TK2MSFTNGP12.phx.gbl...
> Hi,
> Sorry for the bad English.
> I need a tool to see the difference between 2 databases.
>
|||Hi,
SQLCompare from Red-gate is an excellant tool to compare data and schema in
sql server databases.
http://www.red-gate.com/SQL_Compare.htm
You can download the 14 day trial and try it out.
Thanks
Hari
SQL Server MVP
"Octavian RUSE" <oruse@.saratoga.ro> wrote in message
news:uZGTQkOQFHA.164@.TK2MSFTNGP12.phx.gbl...
> Hi,
> Sorry for the bad English.
> I need a tool to see the difference between 2 databases.
>
|||DB Ghost does comparison and much, much more...
regards,
Mark Baekdal
http://www.dbghost.com
http://www.innovartis.co.uk
+44 (0)208 241 1762
Build, Comparison and Synchronization from Source Control = Database change
management for SQL Server
"Octavian RUSE" wrote:
> Hi,
> Sorry for the bad English.
> I need a tool to see the difference between 2 databases.
>
>
Showing posts with label english. Show all posts
Showing posts with label english. Show all posts
Sunday, March 25, 2012
Thursday, March 22, 2012
difference
hello!
sorry, i don´t speak english.
hello again!
It what differs it is between these two sentence?
- exec (' exec sp_MShelpindexPru cliente,'+''+@.indexid+''+'output')
-exec sp_MShelpindexPru cliente,@.indexid output
Supposedly, they are equal , no?
None gives me mistake, but The first one does not give me a result And
the second one gives me the correct result. Which is the difference
between both?
I need to do it of the second form, because I need to insert one it
use @.dbname initially.
Thank you very much, and excuses me for my English. :-(Look into using sp_execute_sql instead. See if this helps:
http://support.microsoft.com/default.aspx?scid=kb;en-us;262499
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
What hardware is your SQL Server running on?
http://vyaskn.tripod.com/poll.htm
<mani14@.begira.com> wrote in message
news:ca48b635.0308190221.9b9a596@.posting.google.com...
hello!
sorry, i don´t speak english.
hello again!
It what differs it is between these two sentence?
- exec (' exec sp_MShelpindexPru cliente,'+''+@.indexid+''+'output')
-exec sp_MShelpindexPru cliente,@.indexid output
Supposedly, they are equal , no?
None gives me mistake, but The first one does not give me a result And
the second one gives me the correct result. Which is the difference
between both?
I need to do it of the second form, because I need to insert one it
use @.dbname initially.
Thank you very much, and excuses me for my English. :-(|||Hello Mani !
But remeber that for SP_executesql the @.string followed to be executed must
be NVARCHAR !
Jens Süßmeyer.
sorry, i don´t speak english.
hello again!
It what differs it is between these two sentence?
- exec (' exec sp_MShelpindexPru cliente,'+''+@.indexid+''+'output')
-exec sp_MShelpindexPru cliente,@.indexid output
Supposedly, they are equal , no?
None gives me mistake, but The first one does not give me a result And
the second one gives me the correct result. Which is the difference
between both?
I need to do it of the second form, because I need to insert one it
use @.dbname initially.
Thank you very much, and excuses me for my English. :-(Look into using sp_execute_sql instead. See if this helps:
http://support.microsoft.com/default.aspx?scid=kb;en-us;262499
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
What hardware is your SQL Server running on?
http://vyaskn.tripod.com/poll.htm
<mani14@.begira.com> wrote in message
news:ca48b635.0308190221.9b9a596@.posting.google.com...
hello!
sorry, i don´t speak english.
hello again!
It what differs it is between these two sentence?
- exec (' exec sp_MShelpindexPru cliente,'+''+@.indexid+''+'output')
-exec sp_MShelpindexPru cliente,@.indexid output
Supposedly, they are equal , no?
None gives me mistake, but The first one does not give me a result And
the second one gives me the correct result. Which is the difference
between both?
I need to do it of the second form, because I need to insert one it
use @.dbname initially.
Thank you very much, and excuses me for my English. :-(|||Hello Mani !
But remeber that for SP_executesql the @.string followed to be executed must
be NVARCHAR !
Jens Süßmeyer.
Monday, March 19, 2012
Dictionarry order question
I have an installed sql server 2000 language English with server collation
set to SQL_Latin1_General_CP1_CI_AS on a W2k server box. There are several
applications running in production using that machine and those settings.
Now the company is getting a new program that has as the requirement for its
sql server dictionary order to be set to Custom, Case insensitive, Accent
insensitive, for use with 1252 character set.
This server has lots of capacity left and there is no way to justify
spending dollars on another processor license for this app when the server
we already have should be able to do the job.
Is it possible to change the dictionary order on the current server and its
databases and test my current apps? If they still work as before I can then
leave it like that, if not I would have to be able to come back to current
settings.
What is the expert opinion on the difference in settings between the new app
and the current settings as shown above, do you think we should try keeping
our current settings for the new app? The app coming in is using asp pages
and the users are all French, the data in the files will be French with
accented characters and also some English in some fields.
Any help would be greatly appreciated,
RD
If it was me, I'd set up a new instance of SQL Server (configured with the
collation sequence of your choice) and let 'er rip. But with SQL Server
2000, it's possible to have different collation sequences on the instance,
database, table, or even column (IIRC). So there's no reason to change your
existing apps and databases. As far as I know, changing collations is a
real pain in the butt, and involves DTS'ing or BCP'ing your data to a new
home, or out to a temporary one, and in to the re-built one.
Clint
"RD" <bdufour@.sgiims.com> wrote in message
news:#OXncM9hFHA.4000@.TK2MSFTNGP12.phx.gbl...
> I have an installed sql server 2000 language English with server collation
> set to SQL_Latin1_General_CP1_CI_AS on a W2k server box. There are several
> applications running in production using that machine and those settings.
> Now the company is getting a new program that has as the requirement for
its
> sql server dictionary order to be set to Custom, Case insensitive, Accent
> insensitive, for use with 1252 character set.
> This server has lots of capacity left and there is no way to justify
> spending dollars on another processor license for this app when the server
> we already have should be able to do the job.
> Is it possible to change the dictionary order on the current server and
its
> databases and test my current apps? If they still work as before I can
then
> leave it like that, if not I would have to be able to come back to current
> settings.
> What is the expert opinion on the difference in settings between the new
app
> and the current settings as shown above, do you think we should try
keeping
> our current settings for the new app? The app coming in is using asp pages
> and the users are all French, the data in the files will be French with
> accented characters and also some English in some fields.
> Any help would be greatly appreciated,
> RD
>
set to SQL_Latin1_General_CP1_CI_AS on a W2k server box. There are several
applications running in production using that machine and those settings.
Now the company is getting a new program that has as the requirement for its
sql server dictionary order to be set to Custom, Case insensitive, Accent
insensitive, for use with 1252 character set.
This server has lots of capacity left and there is no way to justify
spending dollars on another processor license for this app when the server
we already have should be able to do the job.
Is it possible to change the dictionary order on the current server and its
databases and test my current apps? If they still work as before I can then
leave it like that, if not I would have to be able to come back to current
settings.
What is the expert opinion on the difference in settings between the new app
and the current settings as shown above, do you think we should try keeping
our current settings for the new app? The app coming in is using asp pages
and the users are all French, the data in the files will be French with
accented characters and also some English in some fields.
Any help would be greatly appreciated,
RD
If it was me, I'd set up a new instance of SQL Server (configured with the
collation sequence of your choice) and let 'er rip. But with SQL Server
2000, it's possible to have different collation sequences on the instance,
database, table, or even column (IIRC). So there's no reason to change your
existing apps and databases. As far as I know, changing collations is a
real pain in the butt, and involves DTS'ing or BCP'ing your data to a new
home, or out to a temporary one, and in to the re-built one.
Clint
"RD" <bdufour@.sgiims.com> wrote in message
news:#OXncM9hFHA.4000@.TK2MSFTNGP12.phx.gbl...
> I have an installed sql server 2000 language English with server collation
> set to SQL_Latin1_General_CP1_CI_AS on a W2k server box. There are several
> applications running in production using that machine and those settings.
> Now the company is getting a new program that has as the requirement for
its
> sql server dictionary order to be set to Custom, Case insensitive, Accent
> insensitive, for use with 1252 character set.
> This server has lots of capacity left and there is no way to justify
> spending dollars on another processor license for this app when the server
> we already have should be able to do the job.
> Is it possible to change the dictionary order on the current server and
its
> databases and test my current apps? If they still work as before I can
then
> leave it like that, if not I would have to be able to come back to current
> settings.
> What is the expert opinion on the difference in settings between the new
app
> and the current settings as shown above, do you think we should try
keeping
> our current settings for the new app? The app coming in is using asp pages
> and the users are all French, the data in the files will be French with
> accented characters and also some English in some fields.
> Any help would be greatly appreciated,
> RD
>
Dictionarry order question
I have an installed sql server 2000 language English with server collation
set to SQL_Latin1_General_CP1_CI_AS on a W2k server box. There are several
applications running in production using that machine and those settings.
Now the company is getting a new program that has as the requirement for its
sql server dictionary order to be set to Custom, Case insensitive, Accent
insensitive, for use with 1252 character set.
This server has lots of capacity left and there is no way to justify
spending dollars on another processor license for this app when the server
we already have should be able to do the job.
Is it possible to change the dictionary order on the current server and its
databases and test my current apps? If they still work as before I can then
leave it like that, if not I would have to be able to come back to current
settings.
What is the expert opinion on the difference in settings between the new app
and the current settings as shown above, do you think we should try keeping
our current settings for the new app? The app coming in is using asp pages
and the users are all French, the data in the files will be French with
accented characters and also some English in some fields.
Any help would be greatly appreciated,
RDIf it was me, I'd set up a new instance of SQL Server (configured with the
collation sequence of your choice) and let 'er rip. But with SQL Server
2000, it's possible to have different collation sequences on the instance,
database, table, or even column (IIRC). So there's no reason to change your
existing apps and databases. As far as I know, changing collations is a
real pain in the butt, and involves DTS'ing or BCP'ing your data to a new
home, or out to a temporary one, and in to the re-built one.
Clint
"RD" <bdufour@.sgiims.com> wrote in message
news:#OXncM9hFHA.4000@.TK2MSFTNGP12.phx.gbl...
> I have an installed sql server 2000 language English with server collation
> set to SQL_Latin1_General_CP1_CI_AS on a W2k server box. There are several
> applications running in production using that machine and those settings.
> Now the company is getting a new program that has as the requirement for
its
> sql server dictionary order to be set to Custom, Case insensitive, Accent
> insensitive, for use with 1252 character set.
> This server has lots of capacity left and there is no way to justify
> spending dollars on another processor license for this app when the server
> we already have should be able to do the job.
> Is it possible to change the dictionary order on the current server and
its
> databases and test my current apps? If they still work as before I can
then
> leave it like that, if not I would have to be able to come back to current
> settings.
> What is the expert opinion on the difference in settings between the new
app
> and the current settings as shown above, do you think we should try
keeping
> our current settings for the new app? The app coming in is using asp pages
> and the users are all French, the data in the files will be French with
> accented characters and also some English in some fields.
> Any help would be greatly appreciated,
> RD
>
set to SQL_Latin1_General_CP1_CI_AS on a W2k server box. There are several
applications running in production using that machine and those settings.
Now the company is getting a new program that has as the requirement for its
sql server dictionary order to be set to Custom, Case insensitive, Accent
insensitive, for use with 1252 character set.
This server has lots of capacity left and there is no way to justify
spending dollars on another processor license for this app when the server
we already have should be able to do the job.
Is it possible to change the dictionary order on the current server and its
databases and test my current apps? If they still work as before I can then
leave it like that, if not I would have to be able to come back to current
settings.
What is the expert opinion on the difference in settings between the new app
and the current settings as shown above, do you think we should try keeping
our current settings for the new app? The app coming in is using asp pages
and the users are all French, the data in the files will be French with
accented characters and also some English in some fields.
Any help would be greatly appreciated,
RDIf it was me, I'd set up a new instance of SQL Server (configured with the
collation sequence of your choice) and let 'er rip. But with SQL Server
2000, it's possible to have different collation sequences on the instance,
database, table, or even column (IIRC). So there's no reason to change your
existing apps and databases. As far as I know, changing collations is a
real pain in the butt, and involves DTS'ing or BCP'ing your data to a new
home, or out to a temporary one, and in to the re-built one.
Clint
"RD" <bdufour@.sgiims.com> wrote in message
news:#OXncM9hFHA.4000@.TK2MSFTNGP12.phx.gbl...
> I have an installed sql server 2000 language English with server collation
> set to SQL_Latin1_General_CP1_CI_AS on a W2k server box. There are several
> applications running in production using that machine and those settings.
> Now the company is getting a new program that has as the requirement for
its
> sql server dictionary order to be set to Custom, Case insensitive, Accent
> insensitive, for use with 1252 character set.
> This server has lots of capacity left and there is no way to justify
> spending dollars on another processor license for this app when the server
> we already have should be able to do the job.
> Is it possible to change the dictionary order on the current server and
its
> databases and test my current apps? If they still work as before I can
then
> leave it like that, if not I would have to be able to come back to current
> settings.
> What is the expert opinion on the difference in settings between the new
app
> and the current settings as shown above, do you think we should try
keeping
> our current settings for the new app? The app coming in is using asp pages
> and the users are all French, the data in the files will be French with
> accented characters and also some English in some fields.
> Any help would be greatly appreciated,
> RD
>
Dictionarry order question
I have an installed sql server 2000 language English with server collation
set to SQL_Latin1_General_CP1_CI_AS on a W2k server box. There are several
applications running in production using that machine and those settings.
Now the company is getting a new program that has as the requirement for its
sql server dictionary order to be set to Custom, Case insensitive, Accent
insensitive, for use with 1252 character set.
This server has lots of capacity left and there is no way to justify
spending dollars on another processor license for this app when the server
we already have should be able to do the job.
Is it possible to change the dictionary order on the current server and its
databases and test my current apps? If they still work as before I can then
leave it like that, if not I would have to be able to come back to current
settings.
What is the expert opinion on the difference in settings between the new app
and the current settings as shown above, do you think we should try keeping
our current settings for the new app? The app coming in is using asp pages
and the users are all French, the data in the files will be French with
accented characters and also some English in some fields.
Any help would be greatly appreciated,
RDIf it was me, I'd set up a new instance of SQL Server (configured with the
collation sequence of your choice) and let 'er rip. But with SQL Server
2000, it's possible to have different collation sequences on the instance,
database, table, or even column (IIRC). So there's no reason to change your
existing apps and databases. As far as I know, changing collations is a
real pain in the butt, and involves DTS'ing or BCP'ing your data to a new
home, or out to a temporary one, and in to the re-built one.
Clint
"RD" <bdufour@.sgiims.com> wrote in message
news:#OXncM9hFHA.4000@.TK2MSFTNGP12.phx.gbl...
> I have an installed sql server 2000 language English with server collation
> set to SQL_Latin1_General_CP1_CI_AS on a W2k server box. There are several
> applications running in production using that machine and those settings.
> Now the company is getting a new program that has as the requirement for
its
> sql server dictionary order to be set to Custom, Case insensitive, Accent
> insensitive, for use with 1252 character set.
> This server has lots of capacity left and there is no way to justify
> spending dollars on another processor license for this app when the server
> we already have should be able to do the job.
> Is it possible to change the dictionary order on the current server and
its
> databases and test my current apps? If they still work as before I can
then
> leave it like that, if not I would have to be able to come back to current
> settings.
> What is the expert opinion on the difference in settings between the new
app
> and the current settings as shown above, do you think we should try
keeping
> our current settings for the new app? The app coming in is using asp pages
> and the users are all French, the data in the files will be French with
> accented characters and also some English in some fields.
> Any help would be greatly appreciated,
> RD
>
set to SQL_Latin1_General_CP1_CI_AS on a W2k server box. There are several
applications running in production using that machine and those settings.
Now the company is getting a new program that has as the requirement for its
sql server dictionary order to be set to Custom, Case insensitive, Accent
insensitive, for use with 1252 character set.
This server has lots of capacity left and there is no way to justify
spending dollars on another processor license for this app when the server
we already have should be able to do the job.
Is it possible to change the dictionary order on the current server and its
databases and test my current apps? If they still work as before I can then
leave it like that, if not I would have to be able to come back to current
settings.
What is the expert opinion on the difference in settings between the new app
and the current settings as shown above, do you think we should try keeping
our current settings for the new app? The app coming in is using asp pages
and the users are all French, the data in the files will be French with
accented characters and also some English in some fields.
Any help would be greatly appreciated,
RDIf it was me, I'd set up a new instance of SQL Server (configured with the
collation sequence of your choice) and let 'er rip. But with SQL Server
2000, it's possible to have different collation sequences on the instance,
database, table, or even column (IIRC). So there's no reason to change your
existing apps and databases. As far as I know, changing collations is a
real pain in the butt, and involves DTS'ing or BCP'ing your data to a new
home, or out to a temporary one, and in to the re-built one.
Clint
"RD" <bdufour@.sgiims.com> wrote in message
news:#OXncM9hFHA.4000@.TK2MSFTNGP12.phx.gbl...
> I have an installed sql server 2000 language English with server collation
> set to SQL_Latin1_General_CP1_CI_AS on a W2k server box. There are several
> applications running in production using that machine and those settings.
> Now the company is getting a new program that has as the requirement for
its
> sql server dictionary order to be set to Custom, Case insensitive, Accent
> insensitive, for use with 1252 character set.
> This server has lots of capacity left and there is no way to justify
> spending dollars on another processor license for this app when the server
> we already have should be able to do the job.
> Is it possible to change the dictionary order on the current server and
its
> databases and test my current apps? If they still work as before I can
then
> leave it like that, if not I would have to be able to come back to current
> settings.
> What is the expert opinion on the difference in settings between the new
app
> and the current settings as shown above, do you think we should try
keeping
> our current settings for the new app? The app coming in is using asp pages
> and the users are all French, the data in the files will be French with
> accented characters and also some English in some fields.
> Any help would be greatly appreciated,
> RD
>
Subscribe to:
Posts (Atom)