Is it possible to Migrate 2005 database to 2000 engine?

Hi,
We have been developing a new database using 2005 with the understanding
that the deployment would be on a 2005 production instance. Now we learn
that the target server is running 2000. We could create a separate 2005
instance on the same server but it seems that the additional administration
of security and object ownership will be more hassle that downgrading the
empty data objects to 2000. So far, the database consists of about 20
tables with accompanying meta data (table/column descriptions). I was
planning to use sql scripts generated in 2005 to recreate the tables on a
2000 instance but realize that some modifications will be required to
recreate the metadata.
Does anyone have any suggestions on the migration of a 2005 database to
2000?
Thanks, Simon
No easy way ... Try your own manual migration and come up with a white
paper ... Read below link
http://searchsqlserver.techtarget.co...301536,00.html
Keppe on posting the issues you face so that we can help...
Thanks,
Sree
[Please specify the version of Sql Server as we can save one thread and time
asking back if its 2000 or 2005]
"Simon" wrote:

> Hi,
> We have been developing a new database using 2005 with the understanding
> that the deployment would be on a 2005 production instance. Now we learn
> that the target server is running 2000. We could create a separate 2005
> instance on the same server but it seems that the additional administration
> of security and object ownership will be more hassle that downgrading the
> empty data objects to 2000. So far, the database consists of about 20
> tables with accompanying meta data (table/column descriptions). I was
> planning to use sql scripts generated in 2005 to recreate the tables on a
> 2000 instance but realize that some modifications will be required to
> recreate the metadata.
> Does anyone have any suggestions on the migration of a 2005 database to
> 2000?
> Thanks, Simon
>
>
sql

Is it possible to Migrate 2005 database to 2000 engine?

Hi,
We have been developing a new database using 2005 with the understanding
that the deployment would be on a 2005 production instance. Now we learn
that the target server is running 2000. We could create a separate 2005
instance on the same server but it seems that the additional administration
of security and object ownership will be more hassle that downgrading the
empty data objects to 2000. So far, the database consists of about 20
tables with accompanying meta data (table/column descriptions). I was
planning to use sql scripts generated in 2005 to recreate the tables on a
2000 instance but realize that some modifications will be required to
recreate the metadata.
Does anyone have any suggestions on the migration of a 2005 database to
2000?
Thanks, SimonNo easy way ... Try your own manual migration and come up with a white
paper ... Read below link
http://searchsqlserver.techtarget.c...x301536,00.html
Keppe on posting the issues you face so that we can help...
Thanks,
Sree
[Please specify the version of Sql Server as we can save one thread and
time
asking back if its 2000 or 2005]
"Simon" wrote:

> Hi,
> We have been developing a new database using 2005 with the understanding
> that the deployment would be on a 2005 production instance. Now we learn
> that the target server is running 2000. We could create a separate 2005
> instance on the same server but it seems that the additional administratio
n
> of security and object ownership will be more hassle that downgrading the
> empty data objects to 2000. So far, the database consists of about 20
> tables with accompanying meta data (table/column descriptions). I was
> planning to use sql scripts generated in 2005 to recreate the tables on a
> 2000 instance but realize that some modifications will be required to
> recreate the metadata.
> Does anyone have any suggestions on the migration of a 2005 database to
> 2000?
> Thanks, Simon
>
>

Is it possible to Migrate 2005 database to 2000 engine?

Hi,
We have been developing a new database using 2005 with the understanding
that the deployment would be on a 2005 production instance. Now we learn
that the target server is running 2000. We could create a separate 2005
instance on the same server but it seems that the additional administration
of security and object ownership will be more hassle that downgrading the
empty data objects to 2000. So far, the database consists of about 20
tables with accompanying meta data (table/column descriptions). I was
planning to use sql scripts generated in 2005 to recreate the tables on a
2000 instance but realize that some modifications will be required to
recreate the metadata.
Does anyone have any suggestions on the migration of a 2005 database to
2000?
Thanks, SimonNo easy way :(... Try your own manual migration and come up with a white
paper :)... Read below link
http://searchsqlserver.techtarget.com/expert/KnowledgebaseAnswer/0,289625,sid87_gci1149585_tax301536,00.html
Keppe on posting the issues you face so that we can help...
--
Thanks,
Sree
[Please specify the version of Sql Server as we can save one thread and time
asking back if its 2000 or 2005]
"Simon" wrote:
> Hi,
> We have been developing a new database using 2005 with the understanding
> that the deployment would be on a 2005 production instance. Now we learn
> that the target server is running 2000. We could create a separate 2005
> instance on the same server but it seems that the additional administration
> of security and object ownership will be more hassle that downgrading the
> empty data objects to 2000. So far, the database consists of about 20
> tables with accompanying meta data (table/column descriptions). I was
> planning to use sql scripts generated in 2005 to recreate the tables on a
> 2000 instance but realize that some modifications will be required to
> recreate the metadata.
> Does anyone have any suggestions on the migration of a 2005 database to
> 2000?
> Thanks, Simon
>
>

Is it neccesary to restart sql server engine after modifying a noise word list?

Hello all,

We are using sql server 2005 for full text searching.

I removed some of the words in the noise word file (noiseENU.txt) and rebuilt the catalog. However i find that the changes made to the noise file do not reflect immediately. I had to restart sql server engine before my queries returned results according to the updated noise list. Is there a workaround for this ( wherein there isnt the neccesity of restarting sql server engine....this is becoming a problem on live environments as i cannot restart the server when needed)?

Thanks in advance,

Harish

In fact you will only have to start the FTS again to reflect the changes. There is no (even no one to me) known way around this.

Jens K. Suessmeyer

http://www.sqlserver2005.de

|||

Thank You.

But i had tried restarting just the FTS service; didn't work out for me until i restarted the sql server engine again