Hello,
I am VERY new to managing a SQL server database, although I'm an ASP programmer, all I've done is basically connected to one using ODBC. Any advice will have to be written as though you are talking to a complete novice.
I am currently setting up a website (hosted elsewhere) which will need data replicated from our company's (SQL server 7.0) database. It will basically list the products we sell.
My predecessor (or someone) has renamed our server. I am told (by a colleague) that this has caused untold grief and it means Replication will not work. Mind you I don't have a clue HOW replication works, but I'm told that this option is OUT, due to this renaming. Has anyone heard of this before ? Is there a way to fix this easily ?
Anyway for this reason I have been forced to update the web server database using other means. I'm currently creating delimited text files from particular tables, FTP'ing them to the host server and scheduling a job to run a DTS package which maps the text file 'columns' to the table fields.
There are however certain tables which need to be sent (using the same method listed above I guess) only occasionally, such as when new a pricing schedule arrives. Uploading the data everyday would be pointless, as they only change every few weeks.
Our pricing schedules have a version number, and the current version can be derived by seeing which version fits the current date.
What I need to do is create a DTS which will get the Current Version, see if it's the same as the 'LAST VERSION UPDATED' (this can be stored in a table or some other way, ie a Global variable if this is possible) and if they vary, then execute a job (to creates the text files, FTP them and run a DTS to update the tables on the Web Server).
Can you see what I'm trying to achieve ? I feel I'm stumbling and bumbling along trying to achieve this and there MUST be a better way to replicate data. Quite simply all I need to do is upload the data of one table EVERY day and upload the data of several tables occassionally (ie when they have changed).
Can someone PLEASE help, there is no one here with much SQL experience.
Thanks in advance,
Brett.
I am VERY new to managing a SQL server database, although I'm an ASP programmer, all I've done is basically connected to one using ODBC. Any advice will have to be written as though you are talking to a complete novice.
I am currently setting up a website (hosted elsewhere) which will need data replicated from our company's (SQL server 7.0) database. It will basically list the products we sell.
My predecessor (or someone) has renamed our server. I am told (by a colleague) that this has caused untold grief and it means Replication will not work. Mind you I don't have a clue HOW replication works, but I'm told that this option is OUT, due to this renaming. Has anyone heard of this before ? Is there a way to fix this easily ?
Anyway for this reason I have been forced to update the web server database using other means. I'm currently creating delimited text files from particular tables, FTP'ing them to the host server and scheduling a job to run a DTS package which maps the text file 'columns' to the table fields.
There are however certain tables which need to be sent (using the same method listed above I guess) only occasionally, such as when new a pricing schedule arrives. Uploading the data everyday would be pointless, as they only change every few weeks.
Our pricing schedules have a version number, and the current version can be derived by seeing which version fits the current date.
What I need to do is create a DTS which will get the Current Version, see if it's the same as the 'LAST VERSION UPDATED' (this can be stored in a table or some other way, ie a Global variable if this is possible) and if they vary, then execute a job (to creates the text files, FTP them and run a DTS to update the tables on the Web Server).
Can you see what I'm trying to achieve ? I feel I'm stumbling and bumbling along trying to achieve this and there MUST be a better way to replicate data. Quite simply all I need to do is upload the data of one table EVERY day and upload the data of several tables occassionally (ie when they have changed).
Can someone PLEASE help, there is no one here with much SQL experience.
Thanks in advance,
Brett.