32 bit DLL in SQL Server 2005 64 bit

Hello,
I have been using a 32 bit DLL in SQL Server 2000 extended stored procedures
and it works just fine. Now I have upgraded my SQL Server 2000 32 bit to SQL
Server 2005 64 bit edition.
The same extended stored procedures now give error when I call them using
sp_OACreate.. It gives the error "Class not registered" even though the DLL
file is present in the "SysWow64" folder and it has been correctly registere
d
using regsvr32.
On a SQL Server 2005 32 bit edition, it works well. So, it is just the SQL
Server 2005 64 bit edition that seems cannot load the 32 bit DLL.. Is that
right?. What options do I have now so that I can continue the use the same 3
2
bit DLLs in 64 bit SQl Server 2005?.
Thanks for any help!
GaneshHi Ganesh
I am not an expert on this but it looks like only 64 but registrations can
be used by sp_OA... but I have not found anything to say that is the case.
John
"Ganesh Muthuvelu" wrote:

> Hello,
> I have been using a 32 bit DLL in SQL Server 2000 extended stored procedur
es
> and it works just fine. Now I have upgraded my SQL Server 2000 32 bit to S
QL
> Server 2005 64 bit edition.
> The same extended stored procedures now give error when I call them using
> sp_OACreate.. It gives the error "Class not registered" even though the DL
L
> file is present in the "SysWow64" folder and it has been correctly registe
red
> using regsvr32.
> On a SQL Server 2005 32 bit edition, it works well. So, it is just the SQL
> Server 2005 64 bit edition that seems cannot load the 32 bit DLL.. Is that
> right?. What options do I have now so that I can continue the use the same
32
> bit DLLs in 64 bit SQl Server 2005?.
> Thanks for any help!
> Ganesh|||For a 64 bit installation, you need 64 bits dll's.
You cannot mix 64 and 32 bit code in one process, that's why you cannot
use 32 bits dll's in a 64 bit process (or vice versa).
Ganesh Muthuvelu wrote:
> Hello,
> I have been using a 32 bit DLL in SQL Server 2000 extended stored procedur
es
> and it works just fine. Now I have upgraded my SQL Server 2000 32 bit to S
QL
> Server 2005 64 bit edition.
> The same extended stored procedures now give error when I call them using
> sp_OACreate.. It gives the error "Class not registered" even though the DL
L
> file is present in the "SysWow64" folder and it has been correctly registe
red
> using regsvr32.
> On a SQL Server 2005 32 bit edition, it works well. So, it is just the SQL
> Server 2005 64 bit edition that seems cannot load the 32 bit DLL.. Is that
> right?. What options do I have now so that I can continue the use the same
32
> bit DLLs in 64 bit SQl Server 2005?.
> Thanks for any help!
> Ganesh

32 bit DLL in SQL Server 2005 64 bit

Hello,
I have been using a 32 bit DLL in SQL Server 2000 extended stored procedures
and it works just fine. Now I have upgraded my SQL Server 2000 32 bit to SQL
Server 2005 64 bit edition.
The same extended stored procedures now give error when I call them using
sp_OACreate.. It gives the error "Class not registered" even though the DLL
file is present in the "SysWow64" folder and it has been correctly registered
using regsvr32.
On a SQL Server 2005 32 bit edition, it works well. So, it is just the SQL
Server 2005 64 bit edition that seems cannot load the 32 bit DLL.. Is that
right?. What options do I have now so that I can continue the use the same 32
bit DLLs in 64 bit SQl Server 2005?.
Thanks for any help!
Ganesh
Hi Ganesh
I am not an expert on this but it looks like only 64 but registrations can
be used by sp_OA... but I have not found anything to say that is the case.
John
"Ganesh Muthuvelu" wrote:

> Hello,
> I have been using a 32 bit DLL in SQL Server 2000 extended stored procedures
> and it works just fine. Now I have upgraded my SQL Server 2000 32 bit to SQL
> Server 2005 64 bit edition.
> The same extended stored procedures now give error when I call them using
> sp_OACreate.. It gives the error "Class not registered" even though the DLL
> file is present in the "SysWow64" folder and it has been correctly registered
> using regsvr32.
> On a SQL Server 2005 32 bit edition, it works well. So, it is just the SQL
> Server 2005 64 bit edition that seems cannot load the 32 bit DLL.. Is that
> right?. What options do I have now so that I can continue the use the same 32
> bit DLLs in 64 bit SQl Server 2005?.
> Thanks for any help!
> Ganesh

32 bit DLL in SQL Server 2005 64 bit

Hello,
I have been using a 32 bit DLL in SQL Server 2000 extended stored procedures
and it works just fine. Now I have upgraded my SQL Server 2000 32 bit to SQL
Server 2005 64 bit edition.
The same extended stored procedures now give error when I call them using
sp_OACreate.. It gives the error "Class not registered" even though the DLL
file is present in the "SysWow64" folder and it has been correctly registered
using regsvr32.
On a SQL Server 2005 32 bit edition, it works well. So, it is just the SQL
Server 2005 64 bit edition that seems cannot load the 32 bit DLL.. Is that
right?. What options do I have now so that I can continue the use the same 32
bit DLLs in 64 bit SQl Server 2005?.
Thanks for any help!
GaneshHi Ganesh
I am not an expert on this but it looks like only 64 but registrations can
be used by sp_OA... but I have not found anything to say that is the case.
John
"Ganesh Muthuvelu" wrote:
> Hello,
> I have been using a 32 bit DLL in SQL Server 2000 extended stored procedures
> and it works just fine. Now I have upgraded my SQL Server 2000 32 bit to SQL
> Server 2005 64 bit edition.
> The same extended stored procedures now give error when I call them using
> sp_OACreate.. It gives the error "Class not registered" even though the DLL
> file is present in the "SysWow64" folder and it has been correctly registered
> using regsvr32.
> On a SQL Server 2005 32 bit edition, it works well. So, it is just the SQL
> Server 2005 64 bit edition that seems cannot load the 32 bit DLL.. Is that
> right?. What options do I have now so that I can continue the use the same 32
> bit DLLs in 64 bit SQl Server 2005?.
> Thanks for any help!
> Ganesh|||For a 64 bit installation, you need 64 bits dll's.
You cannot mix 64 and 32 bit code in one process, that's why you cannot
use 32 bits dll's in a 64 bit process (or vice versa).
Ganesh Muthuvelu wrote:
> Hello,
> I have been using a 32 bit DLL in SQL Server 2000 extended stored procedures
> and it works just fine. Now I have upgraded my SQL Server 2000 32 bit to SQL
> Server 2005 64 bit edition.
> The same extended stored procedures now give error when I call them using
> sp_OACreate.. It gives the error "Class not registered" even though the DLL
> file is present in the "SysWow64" folder and it has been correctly registered
> using regsvr32.
> On a SQL Server 2005 32 bit edition, it works well. So, it is just the SQL
> Server 2005 64 bit edition that seems cannot load the 32 bit DLL.. Is that
> right?. What options do I have now so that I can continue the use the same 32
> bit DLLs in 64 bit SQl Server 2005?.
> Thanks for any help!
> Ganeshsql

2005 Transactional Replication Performance Problems - help please

I have just upgraded from 2000 to 2005 and my transactional replication is running very slow, I already have a latency of 10 mins and its getting worse. I'm just using the default agent profile, is there anything I need to change?

Help please.

Hi Colschmoll,

which build are u use in your 2005 environment?

|||

This was caused by a trigger on one of my replicated tables. It total killed my distibution agent performance, once removed it latency went from 20 mins to 3 seconds in about 10 seconds!!!

Any idea why these triggers worked fin in SQL 2000?

|||

Hello,

I'am on build 9.0.3054.

|||try to find a specifc cumulative hotfix to solve you problem.|||

try to find on this link:

http://support.microsoft.com/default.aspx/kb/936305/

|||

Can you be a little more specific? What triggers?

|||

A bespoke trigger I had on one of the subscriber tables. It was inserting data into another table on the subscriber database. Why this was causing a problem in 2K5, but was okay in 2K is a mystery to me, any ideas?

|||

Did u alread see if is there triggers enabled to replicate from publisher to subscriber?

|||

It's using Stored Procedures to replicate.

|||

Sorry, I would mean that, if your publications has tables with triggers, if you dont want that this trigges going to subscribers you have to configure it to "not for replication".My question was about it.

|||

The trigger which was causing the problem was on the subscriber table?

2005 SP1 (remote Reporting Services upgrade failures)

Why can it never be easy? I applied SP1 to one of our 2005 database servers and upgraded all components successfully. However when trying to install on a stand alone Reporting Services instance that uses the above database server I can't get past the Login verification. Windows or Sql...Per the ReadMe I am using an acccount that is administrator on both servers and sysadmin in sql, also am running the exe as same admin account.

There are no logs under %Program Files%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files but I found this error in the hotfix log.

[SQL Native Client]TCP Provider: The requested address is not valid in
its context.
[SQL Native Client]Login timeout expired
[SQL Native Client]An error has occurred while establishing a
connection to the server. When connecting to SQL Server 2005, this
failure may be caused by the fact that under the default settings SQL
Server does not allow remote connections.

Verified that the SQL Server allows remote connections (TCP\IP is enabled, Named Pipes is not); even started the Browser sevice that hasn't been running and still get the same error.

Will the steps outlined by Lukasz at http://blogs.msdn.com/lukaszp/archive/2006/05/18/601340.aspx solve my problem or will I still need to upgrade the RS files somehow? I think I belong to 'Sometimes does not work" #3. The Native Client upgrade runs fine by itself.

Advice and commiserations appreciated.

AB

Solved error above by recreating the client alias to the sql server. The port designation had disappeared even though it was default port.

Now am experiencing locked file errors - SQL Reporting Services service is disabled and the web site is stopped. What other services need to be stopped? Do services on the remote sql server also need to be stopped?

AB

2005 SP1

Why can it never be easy? I applied SP1 to one of our 2005 database servers and upgraded all components successfully. However when trying to install on a stand alone Reporting Services instance that uses the above database server I can't get past the Login verification. Windows or Sql...Per the ReadMe I am using an acccount that is administrator on both servers and sysadmin in sql, also am running the exe as same admin account.

There are no logs under %Program Files%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files but I found this error in the hotfix log.

[SQL Native Client]TCP Provider: The requested address is not valid in
its context.
[SQL Native Client]Login timeout expired
[SQL Native Client]An error has occurred while establishing a
connection to the server. When connecting to SQL Server 2005, this
failure may be caused by the fact that under the default settings SQL
Server does not allow remote connections.

Verified that the SQL Server allows remote connections (TCP\IP is enabled, Named Pipes is not); even started the Browser sevice that hasn't been running and still get the same error.

Will the steps outlined by Lukasz at http://blogs.msdn.com/lukaszp/archive/2006/05/18/601340.aspx solve my problem or will I still need to upgrade the RS files somehow? I think I belong to 'Sometimes does not work" #3. The Native Client upgrade runs fine by itself.

Advice and commiserations appreciated.

AB

Solved error above by recreating the client alias to the sql server. The port designation had disappeared even though it was default port.

Now am experiencing locked file errors - SQL Reporting Services service is disabled and the web site is stopped. What other services need to be stopped? Do services on the remote sql server also need to be stopped?

AB

2005 Log Reader

We are having a problem with a recently upgraded 2005 replication setup. We
didn't actually migrate to the new version, but rather started from a clean
operating system and SQL installation, just upgrading the databases. I took
the precaution of clearing down all the replication before commencing and
things were looking fine until the following error messages started to
appear. These are fairly consistent, in that the reference the same numbers
etc.
records scanned in pass # 1, elapsed time 1531 (ms).'.
2006-12-19 13:04:47.913 Status: 0, code: 20011, text: 'The process could not
execute 'sp_replcmds' on 'PASASERV\PASLIVE'.'.
2006-12-19 13:04:47.913 The process could not execute 'sp_replcmds' on
'PASASERV\PASLIVE'.
2006-12-19 13:04:47.913 Status: 0, code: 18764, text: 'Execution of filter
stored procedure 1279200203 failed. See the SQL Server errorlog for more
information.'.
2006-12-19 13:04:47.913 Status: 0, code: 18805, text: 'Logreader failed to
construct replicated command from LSN {0000534e:00001a64:0019}.'.
2006-12-19 13:04:47.913 Status: 0, code: 22037, text: 'The process could not
execute 'sp_replcmds' on 'PASASERV\PASLIVE'.'.
records scanned in pass # 1, elapsed time 1531 (ms).'.
2006-12-19 13:04:47.913 Status: 0, code: 20011, text: 'The process could not
execute 'sp_replcmds' on 'PASASERV\PASLIVE'.'.
2006-12-19 13:04:47.913 The process could not execute 'sp_replcmds' on
'PASASERV\PASLIVE'.
2006-12-19 13:04:47.913 Status: 0, code: 18764, text: 'Execution of filter
stored procedure 1279200203 failed. See the SQL Server errorlog for more
information.'.
2006-12-19 13:04:47.913 Status: 0, code: 18805, text: 'Logreader failed to
construct replicated command from LSN {0000534e:00001a64:0019}.'.
The SQL Server error log is no more revealing: -
2006-12-19 13:04:47.913 Status: 0, code: 22037, text: 'The process could not
execute 'sp_replcmds' on 'PASASERV\PASLIVE'.'.
records scanned in pass # 1, elapsed time 1531 (ms).'.
2006-12-19 13:04:47.913 Status: 0, code: 20011, text: 'The process could not
execute 'sp_replcmds' on 'PASASERV\PASLIVE'.'.
2006-12-19 13:04:47.913 The process could not execute 'sp_replcmds' on
'PASASERV\PASLIVE'.
2006-12-19 13:04:47.913 Status: 0, code: 18764, text: 'Execution of filter
stored procedure 1279200203 failed. See the SQL Server errorlog for more
information.'.
2006-12-19 13:04:47.913 Status: 0, code: 18805, text: 'Logreader failed to
construct replicated command from LSN {0000534e:00001a64:0019}.'.
2006-12-19 13:04:47.913 Status: 0, code: 22037, text: 'The process could not
execute 'sp_replcmds' on 'PASASERV\PASLIVE'.'.
The first time this happened, I eventually decided to remove all the
replication and start again, but I can't really afford to do this again.
Also, it's a production system and we don't want to have to downgrade as it
worked fine in testing.
The only thing I can think of that might be causing it is some of the later
publications I am adding (maybe the word filter is significant?) as when I
add my initial set of publications it seems to be going fine, only messing up
later.
Any help or suggestions on this would most be gratefully received. I have
only slept about 3 hours for the last couple of nights, trying to get this
resolved. So much for a weekend upgrade ...
It might be a filter problem. Are you using filtering? The last time I ran
into the could not construct replicated command was when I was replicating
text in SQL 7.
Can you try to see if anything works? If it works intermittently, which it
appears to do, you need to isolate the command which is causing the log
reader to fail.
I would strongly recommend opening a support incident with PSS.
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
"Adam Sewell" <Adam Sewell@.discussions.microsoft.com> wrote in message
news:37B4B5B8-D617-4101-BA6D-2FBAAA1DB00F@.microsoft.com...
> We are having a problem with a recently upgraded 2005 replication setup.
> We
> didn't actually migrate to the new version, but rather started from a
> clean
> operating system and SQL installation, just upgrading the databases. I
> took
> the precaution of clearing down all the replication before commencing and
> things were looking fine until the following error messages started to
> appear. These are fairly consistent, in that the reference the same
> numbers
> etc.
> records scanned in pass # 1, elapsed time 1531 (ms).'.
> 2006-12-19 13:04:47.913 Status: 0, code: 20011, text: 'The process could
> not
> execute 'sp_replcmds' on 'PASASERV\PASLIVE'.'.
> 2006-12-19 13:04:47.913 The process could not execute 'sp_replcmds' on
> 'PASASERV\PASLIVE'.
> 2006-12-19 13:04:47.913 Status: 0, code: 18764, text: 'Execution of filter
> stored procedure 1279200203 failed. See the SQL Server errorlog for more
> information.'.
> 2006-12-19 13:04:47.913 Status: 0, code: 18805, text: 'Logreader failed to
> construct replicated command from LSN {0000534e:00001a64:0019}.'.
> 2006-12-19 13:04:47.913 Status: 0, code: 22037, text: 'The process could
> not
> execute 'sp_replcmds' on 'PASASERV\PASLIVE'.'.
> records scanned in pass # 1, elapsed time 1531 (ms).'.
> 2006-12-19 13:04:47.913 Status: 0, code: 20011, text: 'The process could
> not
> execute 'sp_replcmds' on 'PASASERV\PASLIVE'.'.
> 2006-12-19 13:04:47.913 The process could not execute 'sp_replcmds' on
> 'PASASERV\PASLIVE'.
> 2006-12-19 13:04:47.913 Status: 0, code: 18764, text: 'Execution of filter
> stored procedure 1279200203 failed. See the SQL Server errorlog for more
> information.'.
> 2006-12-19 13:04:47.913 Status: 0, code: 18805, text: 'Logreader failed to
> construct replicated command from LSN {0000534e:00001a64:0019}.'.
> The SQL Server error log is no more revealing: -
> 2006-12-19 13:04:47.913 Status: 0, code: 22037, text: 'The process could
> not
> execute 'sp_replcmds' on 'PASASERV\PASLIVE'.'.
> records scanned in pass # 1, elapsed time 1531 (ms).'.
> 2006-12-19 13:04:47.913 Status: 0, code: 20011, text: 'The process could
> not
> execute 'sp_replcmds' on 'PASASERV\PASLIVE'.'.
> 2006-12-19 13:04:47.913 The process could not execute 'sp_replcmds' on
> 'PASASERV\PASLIVE'.
> 2006-12-19 13:04:47.913 Status: 0, code: 18764, text: 'Execution of filter
> stored procedure 1279200203 failed. See the SQL Server errorlog for more
> information.'.
> 2006-12-19 13:04:47.913 Status: 0, code: 18805, text: 'Logreader failed to
> construct replicated command from LSN {0000534e:00001a64:0019}.'.
> 2006-12-19 13:04:47.913 Status: 0, code: 22037, text: 'The process could
> not
> execute 'sp_replcmds' on 'PASASERV\PASLIVE'.'.
> The first time this happened, I eventually decided to remove all the
> replication and start again, but I can't really afford to do this again.
> Also, it's a production system and we don't want to have to downgrade as
> it
> worked fine in testing.
> The only thing I can think of that might be causing it is some of the
> later
> publications I am adding (maybe the word filter is significant?) as when I
> add my initial set of publications it seems to be going fine, only messing
> up
> later.
> Any help or suggestions on this would most be gratefully received. I have
> only slept about 3 hours for the last couple of nights, trying to get this
> resolved. So much for a weekend upgrade ...
|||Hi Hilary,
Thanks for responding as usual.
I am thinking 'filter' too, because I am using filters. They used to work
under 2000 with no trouble and I built the publications fresh using the SQL
Management thing for 2005 and then asked it to script them. Although I am
not a massive fan of the scripts it produces, they are better than the
retrospective ones with loads of superfluous and often downright dangerous
parameters
There are a couple of filters I'm using that I'm worried about. On one of
the tables is: -
StockCode IN(SELECT StockCode FROM Holdings WHERE CompanyCode = 'C'
AND(UnconfirmedHoldingsUnits <> 0 OR ConfirmedHoldingUnits <> 0) AND(
StartDate >= '2004-01-01' OR ISNULL(EndDate, '2029-01-01') >= '2004-12-31')
The other is: -
WHERE CompanyCode IN(SELECT CompanyCode FROM vw_PFS_Companies)
vw_PFS_Companies is a really simple subset view.
There's nothing more complicated than those and they used to work ...
Adam
"Hilary Cotter" wrote:

> It might be a filter problem. Are you using filtering? The last time I ran
> into the could not construct replicated command was when I was replicating
> text in SQL 7.
> Can you try to see if anything works? If it works intermittently, which it
> appears to do, you need to isolate the command which is causing the log
> reader to fail.
> I would strongly recommend opening a support incident with PSS.
> --
> 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
>
> "Adam Sewell" <Adam Sewell@.discussions.microsoft.com> wrote in message
> news:37B4B5B8-D617-4101-BA6D-2FBAAA1DB00F@.microsoft.com...
>
>
|||Filters can be tricky - you might be returning more than one row in your
filter condition. Run profiler to see if you can detect the problem command.
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
"Adam Sewell" <AdamSewell@.discussions.microsoft.com> wrote in message
news:0949A8DB-5A43-43ED-B8E6-7EEFB7789683@.microsoft.com...[vbcol=seagreen]
> Hi Hilary,
> Thanks for responding as usual.
> I am thinking 'filter' too, because I am using filters. They used to work
> under 2000 with no trouble and I built the publications fresh using the
> SQL
> Management thing for 2005 and then asked it to script them. Although I am
> not a massive fan of the scripts it produces, they are better than the
> retrospective ones with loads of superfluous and often downright dangerous
> parameters
> There are a couple of filters I'm using that I'm worried about. On one
> of
> the tables is: -
> StockCode IN(SELECT StockCode FROM Holdings WHERE CompanyCode = 'C'
> AND(UnconfirmedHoldingsUnits <> 0 OR ConfirmedHoldingUnits <> 0) AND(
> StartDate >= '2004-01-01' OR ISNULL(EndDate, '2029-01-01') >=
> '2004-12-31')
> The other is: -
> WHERE CompanyCode IN(SELECT CompanyCode FROM vw_PFS_Companies)
> vw_PFS_Companies is a really simple subset view.
> There's nothing more complicated than those and they used to work ...
>
> Adam
> "Hilary Cotter" wrote:

2005 Copy database objects from one server to another

I just upgraded to SQLServer 2005 Standard. I do development in a database
on one server. When a solution is completely tested, I move it to the
operational database on a different server. With SQLServer 2000, I could
just open the .adp file and do File->Get External Data->Import to move the
objects. That does not work with 2005.
What is the recommended method for moving objects from one database to
another? Obviously, the objects that changed will not be the same every time.
Thanks!
Jer
Jerry
You can script out the objects defenition and run it on destination server.
You may want to keep your object's version on VSS to take over deployment
"JerryWendell" <JerryWendell@.discussions.microsoft.com> wrote in message
news:53AA0759-AEEE-4EA9-AAFE-87902B11A8E8@.microsoft.com...
>I just upgraded to SQLServer 2005 Standard. I do development in a database
> on one server. When a solution is completely tested, I move it to the
> operational database on a different server. With SQLServer 2000, I could
> just open the .adp file and do File->Get External Data->Import to move the
> objects. That does not work with 2005.
> What is the recommended method for moving objects from one database to
> another? Obviously, the objects that changed will not be the same every
> time.
> Thanks!
> Jer

2005 Copy database objects from one server to another

I just upgraded to SQLServer 2005 Standard. I do development in a database
on one server. When a solution is completely tested, I move it to the
operational database on a different server. With SQLServer 2000, I could
just open the .adp file and do File->Get External Data->Import to move the
objects. That does not work with 2005.
What is the recommended method for moving objects from one database to
another? Obviously, the objects that changed will not be the same every tim
e.
Thanks!
JerJerry
You can script out the objects defenition and run it on destination server.
You may want to keep your object's version on VSS to take over deployment
"JerryWendell" <JerryWendell@.discussions.microsoft.com> wrote in message
news:53AA0759-AEEE-4EA9-AAFE-87902B11A8E8@.microsoft.com...
>I just upgraded to SQLServer 2005 Standard. I do development in a database
> on one server. When a solution is completely tested, I move it to the
> operational database on a different server. With SQLServer 2000, I could
> just open the .adp file and do File->Get External Data->Import to move the
> objects. That does not work with 2005.
> What is the recommended method for moving objects from one database to
> another? Obviously, the objects that changed will not be the same every
> time.
> Thanks!
> Jer

2005 Copy database objects from one server to another

I just upgraded to SQLServer 2005 Standard. I do development in a
database on one server. When a solution is completely tested, I move
it to the operational database on a different server. With SQLServer
2000, I could just open the .adp file and do File->Get External
Data->Import to move the objects. That does not work with 2005.
What is the recommended method for moving objects from one database to
another? Obviously, the objects that changed will not be the same
every time.
Thanks!
JerJer (jerry.w.black@.saic.com) writes:

Quote:

Originally Posted by

I just upgraded to SQLServer 2005 Standard. I do development in a
database on one server. When a solution is completely tested, I move
it to the operational database on a different server. With SQLServer
2000, I could just open the .adp file and do File->Get External
Data->Import to move the objects. That does not work with 2005.
What is the recommended method for moving objects from one database to
another? Obviously, the objects that changed will not be the same
every time.

The recommended method is to have all SQL objects under version control
and build all install kits from the version-control system.

At http://www.red-gate.com you can find SQL Compare, which many people
use for this sort of thing.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||Jer wrote:

Quote:

Originally Posted by

I just upgraded to SQLServer 2005 Standard. I do development in a
database on one server. When a solution is completely tested, I move
it to the operational database on a different server. With SQLServer
2000, I could just open the .adp file and do File->Get External
Data->Import to move the objects. That does not work with 2005.
What is the recommended method for moving objects from one database to
another? Obviously, the objects that changed will not be the same
every time.
Thanks!
Jer

A better tool for handling changes via source control is DB Ghost from
Innovartis (http://www.dbghost.com/ggroups) - Red Gate's tools do not
work with source control and thus provide no audit trail whatsoever so
Erland's advice is slightly misleading (sorry Erland, this isn't a
personal attack you just need to understand what Red Gate's tool's
capabilities and limitations are).

Regards,

Malcolm (www.innovartis.co.uk)