I am trying to determine how best to create a query that will allow me to perform 'joins across servers'.
I want to create a single join that will join my production database (Oracle) with my Land Database (MSSQL) on a common key.
From what I have gathered on other sites, it appears that SQLServer can perform this function, but I am not that technical and I am not a SQL programmer (eventhough I have access to one), and I am hoping there are some point and click apps that will let me perform this function.
Any thoughts ?Hello,
the best way to join two databases for example from Oracle to MSSQL is to use ADBC. ADBC is a software package that expands the Oracle database. Once installed, you can select the MSSQL tables that should be visible in Oracle.
If you like, we can assist you installing ADBC and developing the necessary functions for MSSQL to Oracle access.
Please send me a mail to m.peter@.alligatorsql.com if you need further help in this way.
Hope that helps ?
Manfred Peter
(Alligator Company Software GmbH)
http://www.alligatorsql.com
Showing posts with label servers. Show all posts
Showing posts with label servers. Show all posts
Friday, March 23, 2012
Monday, March 12, 2012
Joining a web farm
I have two servers in a web farm. Installation went fine on both servers and
got the first one working. When activating the second server from the first
with "rsconfig -m <RemoteMachineName> etc. I get the error message " Failure
obtaining information from remote WMI provider: Unable to find Reporting
Services WMI namespace on <machinename>. Reporting services may not be
installed."
WMI service and reportserver service is running.Dear Victoria,
We banged our heads against the wall with this problem.
At the end of the day this is what helped us
IN EXACTLY this sequence. If you get the sequence off it will not work.
1. Delete the two GUID entries from the keys table corresponding to the node
you want to reactivae.
2. transfer the symmetric key from the server that is working to the server
that is not working with the RSkeymgmt Utility.
i.e.
a. run:
RSkeymgmt -e -fc:\keys.txt
-ppassword
(this line should have only
three spaces)
on the valid server (farm member)
b. copy the keys.txt file over to the
server you are
trying to reactivate.
c. run
RSkeymgmt -a fc:\keys.txt
-ppassword
on the server you are trying to
reactivate.
d. Restart the ReportServer
e.run the rsreactivate Utility from the
server that is a valid farm member
(it should work at this point)
"Victoria" wrote:
> I have two servers in a web farm. Installation went fine on both servers and
> got the first one working. When activating the second server from the first
> with "rsconfig -m <RemoteMachineName> etc. I get the error message " Failure
> obtaining information from remote WMI provider: Unable to find Reporting
> Services WMI namespace on <machinename>. Reporting services may not be
> installed."
> WMI service and reportserver service is running.
>
got the first one working. When activating the second server from the first
with "rsconfig -m <RemoteMachineName> etc. I get the error message " Failure
obtaining information from remote WMI provider: Unable to find Reporting
Services WMI namespace on <machinename>. Reporting services may not be
installed."
WMI service and reportserver service is running.Dear Victoria,
We banged our heads against the wall with this problem.
At the end of the day this is what helped us
IN EXACTLY this sequence. If you get the sequence off it will not work.
1. Delete the two GUID entries from the keys table corresponding to the node
you want to reactivae.
2. transfer the symmetric key from the server that is working to the server
that is not working with the RSkeymgmt Utility.
i.e.
a. run:
RSkeymgmt -e -fc:\keys.txt
-ppassword
(this line should have only
three spaces)
on the valid server (farm member)
b. copy the keys.txt file over to the
server you are
trying to reactivate.
c. run
RSkeymgmt -a fc:\keys.txt
-ppassword
on the server you are trying to
reactivate.
d. Restart the ReportServer
e.run the rsreactivate Utility from the
server that is a valid farm member
(it should work at this point)
"Victoria" wrote:
> I have two servers in a web farm. Installation went fine on both servers and
> got the first one working. When activating the second server from the first
> with "rsconfig -m <RemoteMachineName> etc. I get the error message " Failure
> obtaining information from remote WMI provider: Unable to find Reporting
> Services WMI namespace on <machinename>. Reporting services may not be
> installed."
> WMI service and reportserver service is running.
>
Joining a domain
One of our SQL servers is not joined to the company domain. We don't know wh
y
the previous IT persons didn't join it to the domain. We're thinking to join
it to the domain now. Is there going to be a problem with that?
Thanks.Hi
There should not be any problem. If you normally use domain accounts for the
services they will probably need to be change. If you change the server name
then you will need to follow
http://msdn2.microsoft.com/en-us/library/ms143799.aspx t o rename the SQL
Server.
John
"lwidjaya" wrote:
> One of our SQL servers is not joined to the company domain. We don't know
why
> the previous IT persons didn't join it to the domain. We're thinking to jo
in
> it to the domain now. Is there going to be a problem with that?
> Thanks.|||Thanks for your answer. Another thing. We have another SQL server for our ER
P
system and we're going to set up a new server with a new name replacing this
server. We have a number of views linked to a database in the old server. Is
there an easy way to update all views with the new server name?
Thanks.
Lisa
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> There should not be any problem. If you normally use domain accounts for t
he
> services they will probably need to be change. If you change the server na
me
> then you will need to follow
> http://msdn2.microsoft.com/en-us/library/ms143799.aspx t o rename the SQL
> Server.
> John
> "lwidjaya" wrote:
>|||Hi Lisa
If your new server has a different name, you would have to create a new
linked server and drop the old one. The views can be scripted and the server
name replaced using an editor; the script(s) can then be run to re-create th
e
views (assuming they are not encrypted views!). You would not need to do the
scripting if you had you the view definitions in source code control.
John
"lwidjaya" wrote:
[vbcol=seagreen]
> Thanks for your answer. Another thing. We have another SQL server for our
ERP
> system and we're going to set up a new server with a new name replacing th
is
> server. We have a number of views linked to a database in the old server.
Is
> there an easy way to update all views with the new server name?
> Thanks.
>
> "John Bell" wrote:
>|||Hi John:
I'm not good in DBA. Could you tell me how to script the views and run it? I
don't think the views are encrypted.
Thanks a lot,
Lisa
"John Bell" wrote:
[vbcol=seagreen]
> Hi Lisa
> If your new server has a different name, you would have to create a new
> linked server and drop the old one. The views can be scripted and the serv
er
> name replaced using an editor; the script(s) can then be run to re-create
the
> views (assuming they are not encrypted views!). You would not need to do t
he
> scripting if you had you the view definitions in source code control.
> John
> "lwidjaya" wrote:
>|||Hi Lisa
The easiest way is to use Enterprise Manager, this assumes you have already
registered the database server.
1. Start Enterprise Manager
2. Open up the tree view so you can see the database you are wishing to
script (Under databases)
3. Right Click the database name and choose All Tasks/Generate SQL Script
4. You will Generate SQL Script dialog. Press the Show All button
5. Choose the All views check box. This will list all the views in the
Objects to be Scripted list box.
6. On the options tab, choose Windows Text (Ansi)
7. Press the OK button, this will prompt you for a file name.
You can then open this file in Query analyser and make the changes needed to
the linked server name.
You don't actually need to change these views if you dropped the existing
linked server and the created the linked server that points to the new
server, but still have the same linked server name as the old server. This
may lead to confusion though!!
HTH
John
"lwidjaya" wrote:
[vbcol=seagreen]
> Hi John:
> I'm not good in DBA. Could you tell me how to script the views and run it?
I
> don't think the views are encrypted.
> Thanks a lot,
> Lisa
> "John Bell" wrote:
>|||Hi John,
thanks for your reply.
So, after I created the script and made the changes, I can just run the
script, right?
Lisa
"John Bell" wrote:
[vbcol=seagreen]
> Hi Lisa
> The easiest way is to use Enterprise Manager, this assumes you have alread
y
> registered the database server.
> 1. Start Enterprise Manager
> 2. Open up the tree view so you can see the database you are wishing to
> script (Under databases)
> 3. Right Click the database name and choose All Tasks/Generate SQL Script
> 4. You will Generate SQL Script dialog. Press the Show All button
> 5. Choose the All views check box. This will list all the views in the
> Objects to be Scripted list box.
> 6. On the options tab, choose Windows Text (Ansi)
> 7. Press the OK button, this will prompt you for a file name.
> You can then open this file in Query analyser and make the changes needed
to
> the linked server name.
> You don't actually need to change these views if you dropped the existing
> linked server and the created the linked server that points to the new
> server, but still have the same linked server name as the old server. This
> may lead to confusion though!!
> HTH
> John
>
> "lwidjaya" wrote:
>|||Hi Lisa
If you have created the linked server, then running the script to drop and
recreate the views in Query analyser should mean you are then using the new
server. Make sure that all the permissions are correct. You may want to do a
test run on a backup//different system before moving the live database.
John
"lwidjaya" wrote:
[vbcol=seagreen]
> Hi John,
> thanks for your reply.
> So, after I created the script and made the changes, I can just run the
> script, right?
> Lisa
> "John Bell" wrote:
>|||Thanks a lot, John!
"John Bell" wrote:
[vbcol=seagreen]
> Hi Lisa
> If you have created the linked server, then running the script to drop and
> recreate the views in Query analyser should mean you are then using the ne
w
> server. Make sure that all the permissions are correct. You may want to do
a
> test run on a backup//different system before moving the live database.
> John
> "lwidjaya" wrote:
>
y
the previous IT persons didn't join it to the domain. We're thinking to join
it to the domain now. Is there going to be a problem with that?
Thanks.Hi
There should not be any problem. If you normally use domain accounts for the
services they will probably need to be change. If you change the server name
then you will need to follow
http://msdn2.microsoft.com/en-us/library/ms143799.aspx t o rename the SQL
Server.
John
"lwidjaya" wrote:
> One of our SQL servers is not joined to the company domain. We don't know
why
> the previous IT persons didn't join it to the domain. We're thinking to jo
in
> it to the domain now. Is there going to be a problem with that?
> Thanks.|||Thanks for your answer. Another thing. We have another SQL server for our ER
P
system and we're going to set up a new server with a new name replacing this
server. We have a number of views linked to a database in the old server. Is
there an easy way to update all views with the new server name?
Thanks.
Lisa
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> There should not be any problem. If you normally use domain accounts for t
he
> services they will probably need to be change. If you change the server na
me
> then you will need to follow
> http://msdn2.microsoft.com/en-us/library/ms143799.aspx t o rename the SQL
> Server.
> John
> "lwidjaya" wrote:
>|||Hi Lisa
If your new server has a different name, you would have to create a new
linked server and drop the old one. The views can be scripted and the server
name replaced using an editor; the script(s) can then be run to re-create th
e
views (assuming they are not encrypted views!). You would not need to do the
scripting if you had you the view definitions in source code control.
John
"lwidjaya" wrote:
[vbcol=seagreen]
> Thanks for your answer. Another thing. We have another SQL server for our
ERP
> system and we're going to set up a new server with a new name replacing th
is
> server. We have a number of views linked to a database in the old server.
Is
> there an easy way to update all views with the new server name?
> Thanks.
>
> "John Bell" wrote:
>|||Hi John:
I'm not good in DBA. Could you tell me how to script the views and run it? I
don't think the views are encrypted.
Thanks a lot,
Lisa
"John Bell" wrote:
[vbcol=seagreen]
> Hi Lisa
> If your new server has a different name, you would have to create a new
> linked server and drop the old one. The views can be scripted and the serv
er
> name replaced using an editor; the script(s) can then be run to re-create
the
> views (assuming they are not encrypted views!). You would not need to do t
he
> scripting if you had you the view definitions in source code control.
> John
> "lwidjaya" wrote:
>|||Hi Lisa
The easiest way is to use Enterprise Manager, this assumes you have already
registered the database server.
1. Start Enterprise Manager
2. Open up the tree view so you can see the database you are wishing to
script (Under databases)
3. Right Click the database name and choose All Tasks/Generate SQL Script
4. You will Generate SQL Script dialog. Press the Show All button
5. Choose the All views check box. This will list all the views in the
Objects to be Scripted list box.
6. On the options tab, choose Windows Text (Ansi)
7. Press the OK button, this will prompt you for a file name.
You can then open this file in Query analyser and make the changes needed to
the linked server name.
You don't actually need to change these views if you dropped the existing
linked server and the created the linked server that points to the new
server, but still have the same linked server name as the old server. This
may lead to confusion though!!
HTH
John
"lwidjaya" wrote:
[vbcol=seagreen]
> Hi John:
> I'm not good in DBA. Could you tell me how to script the views and run it?
I
> don't think the views are encrypted.
> Thanks a lot,
> Lisa
> "John Bell" wrote:
>|||Hi John,
thanks for your reply.
So, after I created the script and made the changes, I can just run the
script, right?
Lisa
"John Bell" wrote:
[vbcol=seagreen]
> Hi Lisa
> The easiest way is to use Enterprise Manager, this assumes you have alread
y
> registered the database server.
> 1. Start Enterprise Manager
> 2. Open up the tree view so you can see the database you are wishing to
> script (Under databases)
> 3. Right Click the database name and choose All Tasks/Generate SQL Script
> 4. You will Generate SQL Script dialog. Press the Show All button
> 5. Choose the All views check box. This will list all the views in the
> Objects to be Scripted list box.
> 6. On the options tab, choose Windows Text (Ansi)
> 7. Press the OK button, this will prompt you for a file name.
> You can then open this file in Query analyser and make the changes needed
to
> the linked server name.
> You don't actually need to change these views if you dropped the existing
> linked server and the created the linked server that points to the new
> server, but still have the same linked server name as the old server. This
> may lead to confusion though!!
> HTH
> John
>
> "lwidjaya" wrote:
>|||Hi Lisa
If you have created the linked server, then running the script to drop and
recreate the views in Query analyser should mean you are then using the new
server. Make sure that all the permissions are correct. You may want to do a
test run on a backup//different system before moving the live database.
John
"lwidjaya" wrote:
[vbcol=seagreen]
> Hi John,
> thanks for your reply.
> So, after I created the script and made the changes, I can just run the
> script, right?
> Lisa
> "John Bell" wrote:
>|||Thanks a lot, John!
"John Bell" wrote:
[vbcol=seagreen]
> Hi Lisa
> If you have created the linked server, then running the script to drop and
> recreate the views in Query analyser should mean you are then using the ne
w
> server. Make sure that all the permissions are correct. You may want to do
a
> test run on a backup//different system before moving the live database.
> John
> "lwidjaya" wrote:
>
Joining a domain
One of our SQL servers is not joined to the company domain. We don't know why
the previous IT persons didn't join it to the domain. We're thinking to join
it to the domain now. Is there going to be a problem with that?
Thanks.Hi
There should not be any problem. If you normally use domain accounts for the
services they will probably need to be change. If you change the server name
then you will need to follow
http://msdn2.microsoft.com/en-us/library/ms143799.aspx t o rename the SQL
Server.
John
"lwidjaya" wrote:
> One of our SQL servers is not joined to the company domain. We don't know why
> the previous IT persons didn't join it to the domain. We're thinking to join
> it to the domain now. Is there going to be a problem with that?
> Thanks.|||Thanks for your answer. Another thing. We have another SQL server for our ERP
system and we're going to set up a new server with a new name replacing this
server. We have a number of views linked to a database in the old server. Is
there an easy way to update all views with the new server name?
Thanks.
Lisa
"John Bell" wrote:
> Hi
> There should not be any problem. If you normally use domain accounts for the
> services they will probably need to be change. If you change the server name
> then you will need to follow
> http://msdn2.microsoft.com/en-us/library/ms143799.aspx t o rename the SQL
> Server.
> John
> "lwidjaya" wrote:
> > One of our SQL servers is not joined to the company domain. We don't know why
> > the previous IT persons didn't join it to the domain. We're thinking to join
> > it to the domain now. Is there going to be a problem with that?
> > Thanks.|||Hi Lisa
If your new server has a different name, you would have to create a new
linked server and drop the old one. The views can be scripted and the server
name replaced using an editor; the script(s) can then be run to re-create the
views (assuming they are not encrypted views!). You would not need to do the
scripting if you had you the view definitions in source code control.
John
"lwidjaya" wrote:
> Thanks for your answer. Another thing. We have another SQL server for our ERP
> system and we're going to set up a new server with a new name replacing this
> server. We have a number of views linked to a database in the old server. Is
> there an easy way to update all views with the new server name?
> Thanks.
>
> "John Bell" wrote:
> > Hi
> >
> > There should not be any problem. If you normally use domain accounts for the
> > services they will probably need to be change. If you change the server name
> > then you will need to follow
> > http://msdn2.microsoft.com/en-us/library/ms143799.aspx t o rename the SQL
> > Server.
> >
> > John
> >
> > "lwidjaya" wrote:
> >
> > > One of our SQL servers is not joined to the company domain. We don't know why
> > > the previous IT persons didn't join it to the domain. We're thinking to join
> > > it to the domain now. Is there going to be a problem with that?
> > > Thanks.|||Hi John:
I'm not good in DBA. Could you tell me how to script the views and run it? I
don't think the views are encrypted.
Thanks a lot,
Lisa
"John Bell" wrote:
> Hi Lisa
> If your new server has a different name, you would have to create a new
> linked server and drop the old one. The views can be scripted and the server
> name replaced using an editor; the script(s) can then be run to re-create the
> views (assuming they are not encrypted views!). You would not need to do the
> scripting if you had you the view definitions in source code control.
> John
> "lwidjaya" wrote:
> > Thanks for your answer. Another thing. We have another SQL server for our ERP
> > system and we're going to set up a new server with a new name replacing this
> > server. We have a number of views linked to a database in the old server. Is
> > there an easy way to update all views with the new server name?
> >
> > Thanks.
> >
> >
> > "John Bell" wrote:
> >
> > > Hi
> > >
> > > There should not be any problem. If you normally use domain accounts for the
> > > services they will probably need to be change. If you change the server name
> > > then you will need to follow
> > > http://msdn2.microsoft.com/en-us/library/ms143799.aspx t o rename the SQL
> > > Server.
> > >
> > > John
> > >
> > > "lwidjaya" wrote:
> > >
> > > > One of our SQL servers is not joined to the company domain. We don't know why
> > > > the previous IT persons didn't join it to the domain. We're thinking to join
> > > > it to the domain now. Is there going to be a problem with that?
> > > > Thanks.|||Hi Lisa
The easiest way is to use Enterprise Manager, this assumes you have already
registered the database server.
1. Start Enterprise Manager
2. Open up the tree view so you can see the database you are wishing to
script (Under databases)
3. Right Click the database name and choose All Tasks/Generate SQL Script
4. You will Generate SQL Script dialog. Press the Show All button
5. Choose the All views check box. This will list all the views in the
Objects to be Scripted list box.
6. On the options tab, choose Windows Text (Ansi)
7. Press the OK button, this will prompt you for a file name.
You can then open this file in Query analyser and make the changes needed to
the linked server name.
You don't actually need to change these views if you dropped the existing
linked server and the created the linked server that points to the new
server, but still have the same linked server name as the old server. This
may lead to confusion though!!
HTH
John
"lwidjaya" wrote:
> Hi John:
> I'm not good in DBA. Could you tell me how to script the views and run it? I
> don't think the views are encrypted.
> Thanks a lot,
> Lisa
> "John Bell" wrote:
> > Hi Lisa
> >
> > If your new server has a different name, you would have to create a new
> > linked server and drop the old one. The views can be scripted and the server
> > name replaced using an editor; the script(s) can then be run to re-create the
> > views (assuming they are not encrypted views!). You would not need to do the
> > scripting if you had you the view definitions in source code control.
> >
> > John
> >
> > "lwidjaya" wrote:
> >
> > > Thanks for your answer. Another thing. We have another SQL server for our ERP
> > > system and we're going to set up a new server with a new name replacing this
> > > server. We have a number of views linked to a database in the old server. Is
> > > there an easy way to update all views with the new server name?
> > >
> > > Thanks.
> > >
> > >
> > > "John Bell" wrote:
> > >
> > > > Hi
> > > >
> > > > There should not be any problem. If you normally use domain accounts for the
> > > > services they will probably need to be change. If you change the server name
> > > > then you will need to follow
> > > > http://msdn2.microsoft.com/en-us/library/ms143799.aspx t o rename the SQL
> > > > Server.
> > > >
> > > > John
> > > >
> > > > "lwidjaya" wrote:
> > > >
> > > > > One of our SQL servers is not joined to the company domain. We don't know why
> > > > > the previous IT persons didn't join it to the domain. We're thinking to join
> > > > > it to the domain now. Is there going to be a problem with that?
> > > > > Thanks.|||Hi John,
thanks for your reply.
So, after I created the script and made the changes, I can just run the
script, right?
Lisa
"John Bell" wrote:
> Hi Lisa
> The easiest way is to use Enterprise Manager, this assumes you have already
> registered the database server.
> 1. Start Enterprise Manager
> 2. Open up the tree view so you can see the database you are wishing to
> script (Under databases)
> 3. Right Click the database name and choose All Tasks/Generate SQL Script
> 4. You will Generate SQL Script dialog. Press the Show All button
> 5. Choose the All views check box. This will list all the views in the
> Objects to be Scripted list box.
> 6. On the options tab, choose Windows Text (Ansi)
> 7. Press the OK button, this will prompt you for a file name.
> You can then open this file in Query analyser and make the changes needed to
> the linked server name.
> You don't actually need to change these views if you dropped the existing
> linked server and the created the linked server that points to the new
> server, but still have the same linked server name as the old server. This
> may lead to confusion though!!
> HTH
> John
>
> "lwidjaya" wrote:
> > Hi John:
> > I'm not good in DBA. Could you tell me how to script the views and run it? I
> > don't think the views are encrypted.
> >
> > Thanks a lot,
> >
> > Lisa
> >
> > "John Bell" wrote:
> >
> > > Hi Lisa
> > >
> > > If your new server has a different name, you would have to create a new
> > > linked server and drop the old one. The views can be scripted and the server
> > > name replaced using an editor; the script(s) can then be run to re-create the
> > > views (assuming they are not encrypted views!). You would not need to do the
> > > scripting if you had you the view definitions in source code control.
> > >
> > > John
> > >
> > > "lwidjaya" wrote:
> > >
> > > > Thanks for your answer. Another thing. We have another SQL server for our ERP
> > > > system and we're going to set up a new server with a new name replacing this
> > > > server. We have a number of views linked to a database in the old server. Is
> > > > there an easy way to update all views with the new server name?
> > > >
> > > > Thanks.
> > > >
> > > >
> > > > "John Bell" wrote:
> > > >
> > > > > Hi
> > > > >
> > > > > There should not be any problem. If you normally use domain accounts for the
> > > > > services they will probably need to be change. If you change the server name
> > > > > then you will need to follow
> > > > > http://msdn2.microsoft.com/en-us/library/ms143799.aspx t o rename the SQL
> > > > > Server.
> > > > >
> > > > > John
> > > > >
> > > > > "lwidjaya" wrote:
> > > > >
> > > > > > One of our SQL servers is not joined to the company domain. We don't know why
> > > > > > the previous IT persons didn't join it to the domain. We're thinking to join
> > > > > > it to the domain now. Is there going to be a problem with that?
> > > > > > Thanks.|||Hi Lisa
If you have created the linked server, then running the script to drop and
recreate the views in Query analyser should mean you are then using the new
server. Make sure that all the permissions are correct. You may want to do a
test run on a backup//different system before moving the live database.
John
"lwidjaya" wrote:
> Hi John,
> thanks for your reply.
> So, after I created the script and made the changes, I can just run the
> script, right?
> Lisa
> "John Bell" wrote:
> > Hi Lisa
> >
> > The easiest way is to use Enterprise Manager, this assumes you have already
> > registered the database server.
> >
> > 1. Start Enterprise Manager
> > 2. Open up the tree view so you can see the database you are wishing to
> > script (Under databases)
> > 3. Right Click the database name and choose All Tasks/Generate SQL Script
> > 4. You will Generate SQL Script dialog. Press the Show All button
> > 5. Choose the All views check box. This will list all the views in the
> > Objects to be Scripted list box.
> > 6. On the options tab, choose Windows Text (Ansi)
> > 7. Press the OK button, this will prompt you for a file name.
> >
> > You can then open this file in Query analyser and make the changes needed to
> > the linked server name.
> >
> > You don't actually need to change these views if you dropped the existing
> > linked server and the created the linked server that points to the new
> > server, but still have the same linked server name as the old server. This
> > may lead to confusion though!!
> >
> > HTH
> >
> > John
> >
> >
> >
> > "lwidjaya" wrote:
> >
> > > Hi John:
> > > I'm not good in DBA. Could you tell me how to script the views and run it? I
> > > don't think the views are encrypted.
> > >
> > > Thanks a lot,
> > >
> > > Lisa
> > >
> > > "John Bell" wrote:
> > >
> > > > Hi Lisa
> > > >
> > > > If your new server has a different name, you would have to create a new
> > > > linked server and drop the old one. The views can be scripted and the server
> > > > name replaced using an editor; the script(s) can then be run to re-create the
> > > > views (assuming they are not encrypted views!). You would not need to do the
> > > > scripting if you had you the view definitions in source code control.
> > > >
> > > > John
> > > >
> > > > "lwidjaya" wrote:
> > > >
> > > > > Thanks for your answer. Another thing. We have another SQL server for our ERP
> > > > > system and we're going to set up a new server with a new name replacing this
> > > > > server. We have a number of views linked to a database in the old server. Is
> > > > > there an easy way to update all views with the new server name?
> > > > >
> > > > > Thanks.
> > > > >
> > > > >
> > > > > "John Bell" wrote:
> > > > >
> > > > > > Hi
> > > > > >
> > > > > > There should not be any problem. If you normally use domain accounts for the
> > > > > > services they will probably need to be change. If you change the server name
> > > > > > then you will need to follow
> > > > > > http://msdn2.microsoft.com/en-us/library/ms143799.aspx t o rename the SQL
> > > > > > Server.
> > > > > >
> > > > > > John
> > > > > >
> > > > > > "lwidjaya" wrote:
> > > > > >
> > > > > > > One of our SQL servers is not joined to the company domain. We don't know why
> > > > > > > the previous IT persons didn't join it to the domain. We're thinking to join
> > > > > > > it to the domain now. Is there going to be a problem with that?
> > > > > > > Thanks.|||Thanks a lot, John!
"John Bell" wrote:
> Hi Lisa
> If you have created the linked server, then running the script to drop and
> recreate the views in Query analyser should mean you are then using the new
> server. Make sure that all the permissions are correct. You may want to do a
> test run on a backup//different system before moving the live database.
> John
> "lwidjaya" wrote:
> > Hi John,
> > thanks for your reply.
> > So, after I created the script and made the changes, I can just run the
> > script, right?
> >
> > Lisa
> >
> > "John Bell" wrote:
> >
> > > Hi Lisa
> > >
> > > The easiest way is to use Enterprise Manager, this assumes you have already
> > > registered the database server.
> > >
> > > 1. Start Enterprise Manager
> > > 2. Open up the tree view so you can see the database you are wishing to
> > > script (Under databases)
> > > 3. Right Click the database name and choose All Tasks/Generate SQL Script
> > > 4. You will Generate SQL Script dialog. Press the Show All button
> > > 5. Choose the All views check box. This will list all the views in the
> > > Objects to be Scripted list box.
> > > 6. On the options tab, choose Windows Text (Ansi)
> > > 7. Press the OK button, this will prompt you for a file name.
> > >
> > > You can then open this file in Query analyser and make the changes needed to
> > > the linked server name.
> > >
> > > You don't actually need to change these views if you dropped the existing
> > > linked server and the created the linked server that points to the new
> > > server, but still have the same linked server name as the old server. This
> > > may lead to confusion though!!
> > >
> > > HTH
> > >
> > > John
> > >
> > >
> > >
> > > "lwidjaya" wrote:
> > >
> > > > Hi John:
> > > > I'm not good in DBA. Could you tell me how to script the views and run it? I
> > > > don't think the views are encrypted.
> > > >
> > > > Thanks a lot,
> > > >
> > > > Lisa
> > > >
> > > > "John Bell" wrote:
> > > >
> > > > > Hi Lisa
> > > > >
> > > > > If your new server has a different name, you would have to create a new
> > > > > linked server and drop the old one. The views can be scripted and the server
> > > > > name replaced using an editor; the script(s) can then be run to re-create the
> > > > > views (assuming they are not encrypted views!). You would not need to do the
> > > > > scripting if you had you the view definitions in source code control.
> > > > >
> > > > > John
> > > > >
> > > > > "lwidjaya" wrote:
> > > > >
> > > > > > Thanks for your answer. Another thing. We have another SQL server for our ERP
> > > > > > system and we're going to set up a new server with a new name replacing this
> > > > > > server. We have a number of views linked to a database in the old server. Is
> > > > > > there an easy way to update all views with the new server name?
> > > > > >
> > > > > > Thanks.
> > > > > >
> > > > > >
> > > > > > "John Bell" wrote:
> > > > > >
> > > > > > > Hi
> > > > > > >
> > > > > > > There should not be any problem. If you normally use domain accounts for the
> > > > > > > services they will probably need to be change. If you change the server name
> > > > > > > then you will need to follow
> > > > > > > http://msdn2.microsoft.com/en-us/library/ms143799.aspx t o rename the SQL
> > > > > > > Server.
> > > > > > >
> > > > > > > John
> > > > > > >
> > > > > > > "lwidjaya" wrote:
> > > > > > >
> > > > > > > > One of our SQL servers is not joined to the company domain. We don't know why
> > > > > > > > the previous IT persons didn't join it to the domain. We're thinking to join
> > > > > > > > it to the domain now. Is there going to be a problem with that?
> > > > > > > > Thanks.
the previous IT persons didn't join it to the domain. We're thinking to join
it to the domain now. Is there going to be a problem with that?
Thanks.Hi
There should not be any problem. If you normally use domain accounts for the
services they will probably need to be change. If you change the server name
then you will need to follow
http://msdn2.microsoft.com/en-us/library/ms143799.aspx t o rename the SQL
Server.
John
"lwidjaya" wrote:
> One of our SQL servers is not joined to the company domain. We don't know why
> the previous IT persons didn't join it to the domain. We're thinking to join
> it to the domain now. Is there going to be a problem with that?
> Thanks.|||Thanks for your answer. Another thing. We have another SQL server for our ERP
system and we're going to set up a new server with a new name replacing this
server. We have a number of views linked to a database in the old server. Is
there an easy way to update all views with the new server name?
Thanks.
Lisa
"John Bell" wrote:
> Hi
> There should not be any problem. If you normally use domain accounts for the
> services they will probably need to be change. If you change the server name
> then you will need to follow
> http://msdn2.microsoft.com/en-us/library/ms143799.aspx t o rename the SQL
> Server.
> John
> "lwidjaya" wrote:
> > One of our SQL servers is not joined to the company domain. We don't know why
> > the previous IT persons didn't join it to the domain. We're thinking to join
> > it to the domain now. Is there going to be a problem with that?
> > Thanks.|||Hi Lisa
If your new server has a different name, you would have to create a new
linked server and drop the old one. The views can be scripted and the server
name replaced using an editor; the script(s) can then be run to re-create the
views (assuming they are not encrypted views!). You would not need to do the
scripting if you had you the view definitions in source code control.
John
"lwidjaya" wrote:
> Thanks for your answer. Another thing. We have another SQL server for our ERP
> system and we're going to set up a new server with a new name replacing this
> server. We have a number of views linked to a database in the old server. Is
> there an easy way to update all views with the new server name?
> Thanks.
>
> "John Bell" wrote:
> > Hi
> >
> > There should not be any problem. If you normally use domain accounts for the
> > services they will probably need to be change. If you change the server name
> > then you will need to follow
> > http://msdn2.microsoft.com/en-us/library/ms143799.aspx t o rename the SQL
> > Server.
> >
> > John
> >
> > "lwidjaya" wrote:
> >
> > > One of our SQL servers is not joined to the company domain. We don't know why
> > > the previous IT persons didn't join it to the domain. We're thinking to join
> > > it to the domain now. Is there going to be a problem with that?
> > > Thanks.|||Hi John:
I'm not good in DBA. Could you tell me how to script the views and run it? I
don't think the views are encrypted.
Thanks a lot,
Lisa
"John Bell" wrote:
> Hi Lisa
> If your new server has a different name, you would have to create a new
> linked server and drop the old one. The views can be scripted and the server
> name replaced using an editor; the script(s) can then be run to re-create the
> views (assuming they are not encrypted views!). You would not need to do the
> scripting if you had you the view definitions in source code control.
> John
> "lwidjaya" wrote:
> > Thanks for your answer. Another thing. We have another SQL server for our ERP
> > system and we're going to set up a new server with a new name replacing this
> > server. We have a number of views linked to a database in the old server. Is
> > there an easy way to update all views with the new server name?
> >
> > Thanks.
> >
> >
> > "John Bell" wrote:
> >
> > > Hi
> > >
> > > There should not be any problem. If you normally use domain accounts for the
> > > services they will probably need to be change. If you change the server name
> > > then you will need to follow
> > > http://msdn2.microsoft.com/en-us/library/ms143799.aspx t o rename the SQL
> > > Server.
> > >
> > > John
> > >
> > > "lwidjaya" wrote:
> > >
> > > > One of our SQL servers is not joined to the company domain. We don't know why
> > > > the previous IT persons didn't join it to the domain. We're thinking to join
> > > > it to the domain now. Is there going to be a problem with that?
> > > > Thanks.|||Hi Lisa
The easiest way is to use Enterprise Manager, this assumes you have already
registered the database server.
1. Start Enterprise Manager
2. Open up the tree view so you can see the database you are wishing to
script (Under databases)
3. Right Click the database name and choose All Tasks/Generate SQL Script
4. You will Generate SQL Script dialog. Press the Show All button
5. Choose the All views check box. This will list all the views in the
Objects to be Scripted list box.
6. On the options tab, choose Windows Text (Ansi)
7. Press the OK button, this will prompt you for a file name.
You can then open this file in Query analyser and make the changes needed to
the linked server name.
You don't actually need to change these views if you dropped the existing
linked server and the created the linked server that points to the new
server, but still have the same linked server name as the old server. This
may lead to confusion though!!
HTH
John
"lwidjaya" wrote:
> Hi John:
> I'm not good in DBA. Could you tell me how to script the views and run it? I
> don't think the views are encrypted.
> Thanks a lot,
> Lisa
> "John Bell" wrote:
> > Hi Lisa
> >
> > If your new server has a different name, you would have to create a new
> > linked server and drop the old one. The views can be scripted and the server
> > name replaced using an editor; the script(s) can then be run to re-create the
> > views (assuming they are not encrypted views!). You would not need to do the
> > scripting if you had you the view definitions in source code control.
> >
> > John
> >
> > "lwidjaya" wrote:
> >
> > > Thanks for your answer. Another thing. We have another SQL server for our ERP
> > > system and we're going to set up a new server with a new name replacing this
> > > server. We have a number of views linked to a database in the old server. Is
> > > there an easy way to update all views with the new server name?
> > >
> > > Thanks.
> > >
> > >
> > > "John Bell" wrote:
> > >
> > > > Hi
> > > >
> > > > There should not be any problem. If you normally use domain accounts for the
> > > > services they will probably need to be change. If you change the server name
> > > > then you will need to follow
> > > > http://msdn2.microsoft.com/en-us/library/ms143799.aspx t o rename the SQL
> > > > Server.
> > > >
> > > > John
> > > >
> > > > "lwidjaya" wrote:
> > > >
> > > > > One of our SQL servers is not joined to the company domain. We don't know why
> > > > > the previous IT persons didn't join it to the domain. We're thinking to join
> > > > > it to the domain now. Is there going to be a problem with that?
> > > > > Thanks.|||Hi John,
thanks for your reply.
So, after I created the script and made the changes, I can just run the
script, right?
Lisa
"John Bell" wrote:
> Hi Lisa
> The easiest way is to use Enterprise Manager, this assumes you have already
> registered the database server.
> 1. Start Enterprise Manager
> 2. Open up the tree view so you can see the database you are wishing to
> script (Under databases)
> 3. Right Click the database name and choose All Tasks/Generate SQL Script
> 4. You will Generate SQL Script dialog. Press the Show All button
> 5. Choose the All views check box. This will list all the views in the
> Objects to be Scripted list box.
> 6. On the options tab, choose Windows Text (Ansi)
> 7. Press the OK button, this will prompt you for a file name.
> You can then open this file in Query analyser and make the changes needed to
> the linked server name.
> You don't actually need to change these views if you dropped the existing
> linked server and the created the linked server that points to the new
> server, but still have the same linked server name as the old server. This
> may lead to confusion though!!
> HTH
> John
>
> "lwidjaya" wrote:
> > Hi John:
> > I'm not good in DBA. Could you tell me how to script the views and run it? I
> > don't think the views are encrypted.
> >
> > Thanks a lot,
> >
> > Lisa
> >
> > "John Bell" wrote:
> >
> > > Hi Lisa
> > >
> > > If your new server has a different name, you would have to create a new
> > > linked server and drop the old one. The views can be scripted and the server
> > > name replaced using an editor; the script(s) can then be run to re-create the
> > > views (assuming they are not encrypted views!). You would not need to do the
> > > scripting if you had you the view definitions in source code control.
> > >
> > > John
> > >
> > > "lwidjaya" wrote:
> > >
> > > > Thanks for your answer. Another thing. We have another SQL server for our ERP
> > > > system and we're going to set up a new server with a new name replacing this
> > > > server. We have a number of views linked to a database in the old server. Is
> > > > there an easy way to update all views with the new server name?
> > > >
> > > > Thanks.
> > > >
> > > >
> > > > "John Bell" wrote:
> > > >
> > > > > Hi
> > > > >
> > > > > There should not be any problem. If you normally use domain accounts for the
> > > > > services they will probably need to be change. If you change the server name
> > > > > then you will need to follow
> > > > > http://msdn2.microsoft.com/en-us/library/ms143799.aspx t o rename the SQL
> > > > > Server.
> > > > >
> > > > > John
> > > > >
> > > > > "lwidjaya" wrote:
> > > > >
> > > > > > One of our SQL servers is not joined to the company domain. We don't know why
> > > > > > the previous IT persons didn't join it to the domain. We're thinking to join
> > > > > > it to the domain now. Is there going to be a problem with that?
> > > > > > Thanks.|||Hi Lisa
If you have created the linked server, then running the script to drop and
recreate the views in Query analyser should mean you are then using the new
server. Make sure that all the permissions are correct. You may want to do a
test run on a backup//different system before moving the live database.
John
"lwidjaya" wrote:
> Hi John,
> thanks for your reply.
> So, after I created the script and made the changes, I can just run the
> script, right?
> Lisa
> "John Bell" wrote:
> > Hi Lisa
> >
> > The easiest way is to use Enterprise Manager, this assumes you have already
> > registered the database server.
> >
> > 1. Start Enterprise Manager
> > 2. Open up the tree view so you can see the database you are wishing to
> > script (Under databases)
> > 3. Right Click the database name and choose All Tasks/Generate SQL Script
> > 4. You will Generate SQL Script dialog. Press the Show All button
> > 5. Choose the All views check box. This will list all the views in the
> > Objects to be Scripted list box.
> > 6. On the options tab, choose Windows Text (Ansi)
> > 7. Press the OK button, this will prompt you for a file name.
> >
> > You can then open this file in Query analyser and make the changes needed to
> > the linked server name.
> >
> > You don't actually need to change these views if you dropped the existing
> > linked server and the created the linked server that points to the new
> > server, but still have the same linked server name as the old server. This
> > may lead to confusion though!!
> >
> > HTH
> >
> > John
> >
> >
> >
> > "lwidjaya" wrote:
> >
> > > Hi John:
> > > I'm not good in DBA. Could you tell me how to script the views and run it? I
> > > don't think the views are encrypted.
> > >
> > > Thanks a lot,
> > >
> > > Lisa
> > >
> > > "John Bell" wrote:
> > >
> > > > Hi Lisa
> > > >
> > > > If your new server has a different name, you would have to create a new
> > > > linked server and drop the old one. The views can be scripted and the server
> > > > name replaced using an editor; the script(s) can then be run to re-create the
> > > > views (assuming they are not encrypted views!). You would not need to do the
> > > > scripting if you had you the view definitions in source code control.
> > > >
> > > > John
> > > >
> > > > "lwidjaya" wrote:
> > > >
> > > > > Thanks for your answer. Another thing. We have another SQL server for our ERP
> > > > > system and we're going to set up a new server with a new name replacing this
> > > > > server. We have a number of views linked to a database in the old server. Is
> > > > > there an easy way to update all views with the new server name?
> > > > >
> > > > > Thanks.
> > > > >
> > > > >
> > > > > "John Bell" wrote:
> > > > >
> > > > > > Hi
> > > > > >
> > > > > > There should not be any problem. If you normally use domain accounts for the
> > > > > > services they will probably need to be change. If you change the server name
> > > > > > then you will need to follow
> > > > > > http://msdn2.microsoft.com/en-us/library/ms143799.aspx t o rename the SQL
> > > > > > Server.
> > > > > >
> > > > > > John
> > > > > >
> > > > > > "lwidjaya" wrote:
> > > > > >
> > > > > > > One of our SQL servers is not joined to the company domain. We don't know why
> > > > > > > the previous IT persons didn't join it to the domain. We're thinking to join
> > > > > > > it to the domain now. Is there going to be a problem with that?
> > > > > > > Thanks.|||Thanks a lot, John!
"John Bell" wrote:
> Hi Lisa
> If you have created the linked server, then running the script to drop and
> recreate the views in Query analyser should mean you are then using the new
> server. Make sure that all the permissions are correct. You may want to do a
> test run on a backup//different system before moving the live database.
> John
> "lwidjaya" wrote:
> > Hi John,
> > thanks for your reply.
> > So, after I created the script and made the changes, I can just run the
> > script, right?
> >
> > Lisa
> >
> > "John Bell" wrote:
> >
> > > Hi Lisa
> > >
> > > The easiest way is to use Enterprise Manager, this assumes you have already
> > > registered the database server.
> > >
> > > 1. Start Enterprise Manager
> > > 2. Open up the tree view so you can see the database you are wishing to
> > > script (Under databases)
> > > 3. Right Click the database name and choose All Tasks/Generate SQL Script
> > > 4. You will Generate SQL Script dialog. Press the Show All button
> > > 5. Choose the All views check box. This will list all the views in the
> > > Objects to be Scripted list box.
> > > 6. On the options tab, choose Windows Text (Ansi)
> > > 7. Press the OK button, this will prompt you for a file name.
> > >
> > > You can then open this file in Query analyser and make the changes needed to
> > > the linked server name.
> > >
> > > You don't actually need to change these views if you dropped the existing
> > > linked server and the created the linked server that points to the new
> > > server, but still have the same linked server name as the old server. This
> > > may lead to confusion though!!
> > >
> > > HTH
> > >
> > > John
> > >
> > >
> > >
> > > "lwidjaya" wrote:
> > >
> > > > Hi John:
> > > > I'm not good in DBA. Could you tell me how to script the views and run it? I
> > > > don't think the views are encrypted.
> > > >
> > > > Thanks a lot,
> > > >
> > > > Lisa
> > > >
> > > > "John Bell" wrote:
> > > >
> > > > > Hi Lisa
> > > > >
> > > > > If your new server has a different name, you would have to create a new
> > > > > linked server and drop the old one. The views can be scripted and the server
> > > > > name replaced using an editor; the script(s) can then be run to re-create the
> > > > > views (assuming they are not encrypted views!). You would not need to do the
> > > > > scripting if you had you the view definitions in source code control.
> > > > >
> > > > > John
> > > > >
> > > > > "lwidjaya" wrote:
> > > > >
> > > > > > Thanks for your answer. Another thing. We have another SQL server for our ERP
> > > > > > system and we're going to set up a new server with a new name replacing this
> > > > > > server. We have a number of views linked to a database in the old server. Is
> > > > > > there an easy way to update all views with the new server name?
> > > > > >
> > > > > > Thanks.
> > > > > >
> > > > > >
> > > > > > "John Bell" wrote:
> > > > > >
> > > > > > > Hi
> > > > > > >
> > > > > > > There should not be any problem. If you normally use domain accounts for the
> > > > > > > services they will probably need to be change. If you change the server name
> > > > > > > then you will need to follow
> > > > > > > http://msdn2.microsoft.com/en-us/library/ms143799.aspx t o rename the SQL
> > > > > > > Server.
> > > > > > >
> > > > > > > John
> > > > > > >
> > > > > > > "lwidjaya" wrote:
> > > > > > >
> > > > > > > > One of our SQL servers is not joined to the company domain. We don't know why
> > > > > > > > the previous IT persons didn't join it to the domain. We're thinking to join
> > > > > > > > it to the domain now. Is there going to be a problem with that?
> > > > > > > > Thanks.
Joining a domain
One of our SQL servers is not joined to the company domain. We don't know why
the previous IT persons didn't join it to the domain. We're thinking to join
it to the domain now. Is there going to be a problem with that?
Thanks.
Hi
There should not be any problem. If you normally use domain accounts for the
services they will probably need to be change. If you change the server name
then you will need to follow
http://msdn2.microsoft.com/en-us/library/ms143799.aspx t o rename the SQL
Server.
John
"lwidjaya" wrote:
> One of our SQL servers is not joined to the company domain. We don't know why
> the previous IT persons didn't join it to the domain. We're thinking to join
> it to the domain now. Is there going to be a problem with that?
> Thanks.
|||Thanks for your answer. Another thing. We have another SQL server for our ERP
system and we're going to set up a new server with a new name replacing this
server. We have a number of views linked to a database in the old server. Is
there an easy way to update all views with the new server name?
Thanks.
Lisa
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> There should not be any problem. If you normally use domain accounts for the
> services they will probably need to be change. If you change the server name
> then you will need to follow
> http://msdn2.microsoft.com/en-us/library/ms143799.aspx t o rename the SQL
> Server.
> John
> "lwidjaya" wrote:
|||Hi Lisa
If your new server has a different name, you would have to create a new
linked server and drop the old one. The views can be scripted and the server
name replaced using an editor; the script(s) can then be run to re-create the
views (assuming they are not encrypted views!). You would not need to do the
scripting if you had you the view definitions in source code control.
John
"lwidjaya" wrote:
[vbcol=seagreen]
> Thanks for your answer. Another thing. We have another SQL server for our ERP
> system and we're going to set up a new server with a new name replacing this
> server. We have a number of views linked to a database in the old server. Is
> there an easy way to update all views with the new server name?
> Thanks.
>
> "John Bell" wrote:
|||Hi John:
I'm not good in DBA. Could you tell me how to script the views and run it? I
don't think the views are encrypted.
Thanks a lot,
Lisa
"John Bell" wrote:
[vbcol=seagreen]
> Hi Lisa
> If your new server has a different name, you would have to create a new
> linked server and drop the old one. The views can be scripted and the server
> name replaced using an editor; the script(s) can then be run to re-create the
> views (assuming they are not encrypted views!). You would not need to do the
> scripting if you had you the view definitions in source code control.
> John
> "lwidjaya" wrote:
|||Hi Lisa
The easiest way is to use Enterprise Manager, this assumes you have already
registered the database server.
1. Start Enterprise Manager
2. Open up the tree view so you can see the database you are wishing to
script (Under databases)
3. Right Click the database name and choose All Tasks/Generate SQL Script
4. You will Generate SQL Script dialog. Press the Show All button
5. Choose the All views check box. This will list all the views in the
Objects to be Scripted list box.
6. On the options tab, choose Windows Text (Ansi)
7. Press the OK button, this will prompt you for a file name.
You can then open this file in Query analyser and make the changes needed to
the linked server name.
You don't actually need to change these views if you dropped the existing
linked server and the created the linked server that points to the new
server, but still have the same linked server name as the old server. This
may lead to confusion though!!
HTH
John
"lwidjaya" wrote:
[vbcol=seagreen]
> Hi John:
> I'm not good in DBA. Could you tell me how to script the views and run it? I
> don't think the views are encrypted.
> Thanks a lot,
> Lisa
> "John Bell" wrote:
|||Hi John,
thanks for your reply.
So, after I created the script and made the changes, I can just run the
script, right?
Lisa
"John Bell" wrote:
[vbcol=seagreen]
> Hi Lisa
> The easiest way is to use Enterprise Manager, this assumes you have already
> registered the database server.
> 1. Start Enterprise Manager
> 2. Open up the tree view so you can see the database you are wishing to
> script (Under databases)
> 3. Right Click the database name and choose All Tasks/Generate SQL Script
> 4. You will Generate SQL Script dialog. Press the Show All button
> 5. Choose the All views check box. This will list all the views in the
> Objects to be Scripted list box.
> 6. On the options tab, choose Windows Text (Ansi)
> 7. Press the OK button, this will prompt you for a file name.
> You can then open this file in Query analyser and make the changes needed to
> the linked server name.
> You don't actually need to change these views if you dropped the existing
> linked server and the created the linked server that points to the new
> server, but still have the same linked server name as the old server. This
> may lead to confusion though!!
> HTH
> John
>
> "lwidjaya" wrote:
|||Hi Lisa
If you have created the linked server, then running the script to drop and
recreate the views in Query analyser should mean you are then using the new
server. Make sure that all the permissions are correct. You may want to do a
test run on a backup//different system before moving the live database.
John
"lwidjaya" wrote:
[vbcol=seagreen]
> Hi John,
> thanks for your reply.
> So, after I created the script and made the changes, I can just run the
> script, right?
> Lisa
> "John Bell" wrote:
|||Thanks a lot, John!
"John Bell" wrote:
[vbcol=seagreen]
> Hi Lisa
> If you have created the linked server, then running the script to drop and
> recreate the views in Query analyser should mean you are then using the new
> server. Make sure that all the permissions are correct. You may want to do a
> test run on a backup//different system before moving the live database.
> John
> "lwidjaya" wrote:
the previous IT persons didn't join it to the domain. We're thinking to join
it to the domain now. Is there going to be a problem with that?
Thanks.
Hi
There should not be any problem. If you normally use domain accounts for the
services they will probably need to be change. If you change the server name
then you will need to follow
http://msdn2.microsoft.com/en-us/library/ms143799.aspx t o rename the SQL
Server.
John
"lwidjaya" wrote:
> One of our SQL servers is not joined to the company domain. We don't know why
> the previous IT persons didn't join it to the domain. We're thinking to join
> it to the domain now. Is there going to be a problem with that?
> Thanks.
|||Thanks for your answer. Another thing. We have another SQL server for our ERP
system and we're going to set up a new server with a new name replacing this
server. We have a number of views linked to a database in the old server. Is
there an easy way to update all views with the new server name?
Thanks.
Lisa
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> There should not be any problem. If you normally use domain accounts for the
> services they will probably need to be change. If you change the server name
> then you will need to follow
> http://msdn2.microsoft.com/en-us/library/ms143799.aspx t o rename the SQL
> Server.
> John
> "lwidjaya" wrote:
|||Hi Lisa
If your new server has a different name, you would have to create a new
linked server and drop the old one. The views can be scripted and the server
name replaced using an editor; the script(s) can then be run to re-create the
views (assuming they are not encrypted views!). You would not need to do the
scripting if you had you the view definitions in source code control.
John
"lwidjaya" wrote:
[vbcol=seagreen]
> Thanks for your answer. Another thing. We have another SQL server for our ERP
> system and we're going to set up a new server with a new name replacing this
> server. We have a number of views linked to a database in the old server. Is
> there an easy way to update all views with the new server name?
> Thanks.
>
> "John Bell" wrote:
|||Hi John:
I'm not good in DBA. Could you tell me how to script the views and run it? I
don't think the views are encrypted.
Thanks a lot,
Lisa
"John Bell" wrote:
[vbcol=seagreen]
> Hi Lisa
> If your new server has a different name, you would have to create a new
> linked server and drop the old one. The views can be scripted and the server
> name replaced using an editor; the script(s) can then be run to re-create the
> views (assuming they are not encrypted views!). You would not need to do the
> scripting if you had you the view definitions in source code control.
> John
> "lwidjaya" wrote:
|||Hi Lisa
The easiest way is to use Enterprise Manager, this assumes you have already
registered the database server.
1. Start Enterprise Manager
2. Open up the tree view so you can see the database you are wishing to
script (Under databases)
3. Right Click the database name and choose All Tasks/Generate SQL Script
4. You will Generate SQL Script dialog. Press the Show All button
5. Choose the All views check box. This will list all the views in the
Objects to be Scripted list box.
6. On the options tab, choose Windows Text (Ansi)
7. Press the OK button, this will prompt you for a file name.
You can then open this file in Query analyser and make the changes needed to
the linked server name.
You don't actually need to change these views if you dropped the existing
linked server and the created the linked server that points to the new
server, but still have the same linked server name as the old server. This
may lead to confusion though!!
HTH
John
"lwidjaya" wrote:
[vbcol=seagreen]
> Hi John:
> I'm not good in DBA. Could you tell me how to script the views and run it? I
> don't think the views are encrypted.
> Thanks a lot,
> Lisa
> "John Bell" wrote:
|||Hi John,
thanks for your reply.
So, after I created the script and made the changes, I can just run the
script, right?
Lisa
"John Bell" wrote:
[vbcol=seagreen]
> Hi Lisa
> The easiest way is to use Enterprise Manager, this assumes you have already
> registered the database server.
> 1. Start Enterprise Manager
> 2. Open up the tree view so you can see the database you are wishing to
> script (Under databases)
> 3. Right Click the database name and choose All Tasks/Generate SQL Script
> 4. You will Generate SQL Script dialog. Press the Show All button
> 5. Choose the All views check box. This will list all the views in the
> Objects to be Scripted list box.
> 6. On the options tab, choose Windows Text (Ansi)
> 7. Press the OK button, this will prompt you for a file name.
> You can then open this file in Query analyser and make the changes needed to
> the linked server name.
> You don't actually need to change these views if you dropped the existing
> linked server and the created the linked server that points to the new
> server, but still have the same linked server name as the old server. This
> may lead to confusion though!!
> HTH
> John
>
> "lwidjaya" wrote:
|||Hi Lisa
If you have created the linked server, then running the script to drop and
recreate the views in Query analyser should mean you are then using the new
server. Make sure that all the permissions are correct. You may want to do a
test run on a backup//different system before moving the live database.
John
"lwidjaya" wrote:
[vbcol=seagreen]
> Hi John,
> thanks for your reply.
> So, after I created the script and made the changes, I can just run the
> script, right?
> Lisa
> "John Bell" wrote:
|||Thanks a lot, John!
"John Bell" wrote:
[vbcol=seagreen]
> Hi Lisa
> If you have created the linked server, then running the script to drop and
> recreate the views in Query analyser should mean you are then using the new
> server. Make sure that all the permissions are correct. You may want to do a
> test run on a backup//different system before moving the live database.
> John
> "lwidjaya" wrote:
Friday, March 9, 2012
Join two views using server aliases
Hello everybody,
I'm working for a hospital and for this job, I created two views using the
server aliases (linked servers).
Both these views are working correctly.
The design of the first view is:
SELECT TOP 100 PERCENT UNID AS ID, SPECIALTY_CODE AS CODE,
SPECIALTY_DESCRIPTION AS NAME
FROM ddsqlGIMS.GIMS.dbo.TBL_SPECIALTY TBL_SPECIALTY_1
ORDER BY SPECIALTY_DESCRIPTION
And for the second view is:
SELECT TOP 100 PERCENT CLINICIAN_ID AS ID, NAME, CLINICIAN_SPEC_CODE AS
SPECIALTY_CODE
FROM ddsqlGIMS.GIMS.dbo.TBL_CLINICIANS TBL_CLINICIANS_1
WHERE (GMC_NO IS NOT NULL) AND (ACTIVE_FLAG = 'Y')
ORDER BY NAME
The problem appaers when I try to join both these views with, for example,
this query:
select c.ID
from VW_CONSULTANTS c
left outer join VW_SPECIALTIES s
on c.SPECIALTY_CODE=s.CODE
I have these error messages:
Server: Msg 8180, Level 16, State 1, Line 1
Statement(s) could not be prepared.
Server: Msg 156, Level 15, State 1, Line 1
Incorrect syntax near the keyword 'ORDER'.
Server: Msg 1033, Level 15, State 1, Line 1
The ORDER BY clause is invalid in views, inline functions, derived tables,
and subqueries, unless TOP is also specified.
For me, the problem is because we try to join two views using server aliases
and the sql server is not successfull in creating the temporary table to put
the results of my select...
But I don't know what I have to do to fix the problem.
Can you help me please?
StF"StF" <StF@.discussions.microsoft.com> wrote in message
news:760671EB-8EC8-4464-8972-D570E0FB2F86@.microsoft.com...
> Hello everybody,
> I'm working for a hospital and for this job, I created two views using the
> server aliases (linked servers).
> Both these views are working correctly.
> The design of the first view is:
> SELECT TOP 100 PERCENT UNID AS ID, SPECIALTY_CODE AS CODE,
> SPECIALTY_DESCRIPTION AS NAME
> FROM ddsqlGIMS.GIMS.dbo.TBL_SPECIALTY TBL_SPECIALTY_1
> ORDER BY SPECIALTY_DESCRIPTION
> And for the second view is:
> SELECT TOP 100 PERCENT CLINICIAN_ID AS ID, NAME, CLINICIAN_SPEC_CODE
> AS
> SPECIALTY_CODE
> FROM ddsqlGIMS.GIMS.dbo.TBL_CLINICIANS TBL_CLINICIANS_1
> WHERE (GMC_NO IS NOT NULL) AND (ACTIVE_FLAG = 'Y')
> ORDER BY NAME
> The problem appaers when I try to join both these views with, for example,
> this query:
> select c.ID
> from VW_CONSULTANTS c
> left outer join VW_SPECIALTIES s
> on c.SPECIALTY_CODE=s.CODE
>
I don't know exactly what's happening, but I know how to fix it.
Don't use TOP 100 PERCENT in a view. It serves absolutely no purpose.
In SQL 2000 this would cause queries against the view to be sorted. But
this behavior was never guaranteed, and it doesn't always happen in 2005.
David|||Thank you very much.
In fact, we use SQL Server 2000 and that's why I used 'TOP 100 PERCENT'.
So, I removed this thing and the 'ORDER BY' and now my select is working.
Thank you again.
StF
"David Browne" wrote:
> "StF" <StF@.discussions.microsoft.com> wrote in message
> news:760671EB-8EC8-4464-8972-D570E0FB2F86@.microsoft.com...
> I don't know exactly what's happening, but I know how to fix it.
> Don't use TOP 100 PERCENT in a view. It serves absolutely no purpose.
> In SQL 2000 this would cause queries against the view to be sorted. But
> this behavior was never guaranteed, and it doesn't always happen in 2005.
> David
>
>
I'm working for a hospital and for this job, I created two views using the
server aliases (linked servers).
Both these views are working correctly.
The design of the first view is:
SELECT TOP 100 PERCENT UNID AS ID, SPECIALTY_CODE AS CODE,
SPECIALTY_DESCRIPTION AS NAME
FROM ddsqlGIMS.GIMS.dbo.TBL_SPECIALTY TBL_SPECIALTY_1
ORDER BY SPECIALTY_DESCRIPTION
And for the second view is:
SELECT TOP 100 PERCENT CLINICIAN_ID AS ID, NAME, CLINICIAN_SPEC_CODE AS
SPECIALTY_CODE
FROM ddsqlGIMS.GIMS.dbo.TBL_CLINICIANS TBL_CLINICIANS_1
WHERE (GMC_NO IS NOT NULL) AND (ACTIVE_FLAG = 'Y')
ORDER BY NAME
The problem appaers when I try to join both these views with, for example,
this query:
select c.ID
from VW_CONSULTANTS c
left outer join VW_SPECIALTIES s
on c.SPECIALTY_CODE=s.CODE
I have these error messages:
Server: Msg 8180, Level 16, State 1, Line 1
Statement(s) could not be prepared.
Server: Msg 156, Level 15, State 1, Line 1
Incorrect syntax near the keyword 'ORDER'.
Server: Msg 1033, Level 15, State 1, Line 1
The ORDER BY clause is invalid in views, inline functions, derived tables,
and subqueries, unless TOP is also specified.
For me, the problem is because we try to join two views using server aliases
and the sql server is not successfull in creating the temporary table to put
the results of my select...
But I don't know what I have to do to fix the problem.
Can you help me please?
StF"StF" <StF@.discussions.microsoft.com> wrote in message
news:760671EB-8EC8-4464-8972-D570E0FB2F86@.microsoft.com...
> Hello everybody,
> I'm working for a hospital and for this job, I created two views using the
> server aliases (linked servers).
> Both these views are working correctly.
> The design of the first view is:
> SELECT TOP 100 PERCENT UNID AS ID, SPECIALTY_CODE AS CODE,
> SPECIALTY_DESCRIPTION AS NAME
> FROM ddsqlGIMS.GIMS.dbo.TBL_SPECIALTY TBL_SPECIALTY_1
> ORDER BY SPECIALTY_DESCRIPTION
> And for the second view is:
> SELECT TOP 100 PERCENT CLINICIAN_ID AS ID, NAME, CLINICIAN_SPEC_CODE
> AS
> SPECIALTY_CODE
> FROM ddsqlGIMS.GIMS.dbo.TBL_CLINICIANS TBL_CLINICIANS_1
> WHERE (GMC_NO IS NOT NULL) AND (ACTIVE_FLAG = 'Y')
> ORDER BY NAME
> The problem appaers when I try to join both these views with, for example,
> this query:
> select c.ID
> from VW_CONSULTANTS c
> left outer join VW_SPECIALTIES s
> on c.SPECIALTY_CODE=s.CODE
>
I don't know exactly what's happening, but I know how to fix it.
Don't use TOP 100 PERCENT in a view. It serves absolutely no purpose.
In SQL 2000 this would cause queries against the view to be sorted. But
this behavior was never guaranteed, and it doesn't always happen in 2005.
David|||Thank you very much.
In fact, we use SQL Server 2000 and that's why I used 'TOP 100 PERCENT'.
So, I removed this thing and the 'ORDER BY' and now my select is working.
Thank you again.
StF
"David Browne" wrote:
> "StF" <StF@.discussions.microsoft.com> wrote in message
> news:760671EB-8EC8-4464-8972-D570E0FB2F86@.microsoft.com...
> I don't know exactly what's happening, but I know how to fix it.
> Don't use TOP 100 PERCENT in a view. It serves absolutely no purpose.
> In SQL 2000 this would cause queries against the view to be sorted. But
> this behavior was never guaranteed, and it doesn't always happen in 2005.
> David
>
>
Join two views using server aliases
Hello everybody,
I'm working for a hospital and for this job, I created two views using the
server aliases (linked servers).
Both these views are working correctly.
The design of the first view is:
SELECT TOP 100 PERCENT UNID AS ID, SPECIALTY_CODE AS CODE,
SPECIALTY_DESCRIPTION AS NAME
FROM ddsqlGIMS.GIMS.dbo.TBL_SPECIALTY TBL_SPECIALTY_1
ORDER BY SPECIALTY_DESCRIPTION
And for the second view is:
SELECT TOP 100 PERCENT CLINICIAN_ID AS ID, NAME, CLINICIAN_SPEC_CODE AS
SPECIALTY_CODE
FROM ddsqlGIMS.GIMS.dbo.TBL_CLINICIANS TBL_CLINICIANS_1
WHERE (GMC_NO IS NOT NULL) AND (ACTIVE_FLAG = 'Y')
ORDER BY NAME
The problem appaers when I try to join both these views with, for example,
this query:
select c.ID
from VW_CONSULTANTS c
left outer join VW_SPECIALTIES s
on c.SPECIALTY_CODE=s.CODE
I have these error messages:
Server: Msg 8180, Level 16, State 1, Line 1
Statement(s) could not be prepared.
Server: Msg 156, Level 15, State 1, Line 1
Incorrect syntax near the keyword 'ORDER'.
Server: Msg 1033, Level 15, State 1, Line 1
The ORDER BY clause is invalid in views, inline functions, derived tables,
and subqueries, unless TOP is also specified.
For me, the problem is because we try to join two views using server aliases
and the sql server is not successfull in creating the temporary table to put
the results of my select...
But I don't know what I have to do to fix the problem.
Can you help me please?
StF"StF" <StF@.discussions.microsoft.com> wrote in message
news:760671EB-8EC8-4464-8972-D570E0FB2F86@.microsoft.com...
> Hello everybody,
> I'm working for a hospital and for this job, I created two views using the
> server aliases (linked servers).
> Both these views are working correctly.
> The design of the first view is:
> SELECT TOP 100 PERCENT UNID AS ID, SPECIALTY_CODE AS CODE,
> SPECIALTY_DESCRIPTION AS NAME
> FROM ddsqlGIMS.GIMS.dbo.TBL_SPECIALTY TBL_SPECIALTY_1
> ORDER BY SPECIALTY_DESCRIPTION
> And for the second view is:
> SELECT TOP 100 PERCENT CLINICIAN_ID AS ID, NAME, CLINICIAN_SPEC_CODE
> AS
> SPECIALTY_CODE
> FROM ddsqlGIMS.GIMS.dbo.TBL_CLINICIANS TBL_CLINICIANS_1
> WHERE (GMC_NO IS NOT NULL) AND (ACTIVE_FLAG = 'Y')
> ORDER BY NAME
> The problem appaers when I try to join both these views with, for example,
> this query:
> select c.ID
> from VW_CONSULTANTS c
> left outer join VW_SPECIALTIES s
> on c.SPECIALTY_CODE=s.CODE
>
I don't know exactly what's happening, but I know how to fix it.
Don't use TOP 100 PERCENT in a view. It serves absolutely no purpose.
In SQL 2000 this would cause queries against the view to be sorted. But
this behavior was never guaranteed, and it doesn't always happen in 2005.
David|||Thank you very much.
In fact, we use SQL Server 2000 and that's why I used 'TOP 100 PERCENT'.
So, I removed this thing and the 'ORDER BY' and now my select is working.
Thank you again.
StF
"David Browne" wrote:
> "StF" <StF@.discussions.microsoft.com> wrote in message
> news:760671EB-8EC8-4464-8972-D570E0FB2F86@.microsoft.com...
> > Hello everybody,
> >
> > I'm working for a hospital and for this job, I created two views using the
> > server aliases (linked servers).
> > Both these views are working correctly.
> >
> > The design of the first view is:
> > SELECT TOP 100 PERCENT UNID AS ID, SPECIALTY_CODE AS CODE,
> > SPECIALTY_DESCRIPTION AS NAME
> > FROM ddsqlGIMS.GIMS.dbo.TBL_SPECIALTY TBL_SPECIALTY_1
> > ORDER BY SPECIALTY_DESCRIPTION
> >
> > And for the second view is:
> > SELECT TOP 100 PERCENT CLINICIAN_ID AS ID, NAME, CLINICIAN_SPEC_CODE
> > AS
> > SPECIALTY_CODE
> > FROM ddsqlGIMS.GIMS.dbo.TBL_CLINICIANS TBL_CLINICIANS_1
> > WHERE (GMC_NO IS NOT NULL) AND (ACTIVE_FLAG = 'Y')
> > ORDER BY NAME
> >
> > The problem appaers when I try to join both these views with, for example,
> > this query:
> > select c.ID
> > from VW_CONSULTANTS c
> > left outer join VW_SPECIALTIES s
> > on c.SPECIALTY_CODE=s.CODE
> >
> I don't know exactly what's happening, but I know how to fix it.
> Don't use TOP 100 PERCENT in a view. It serves absolutely no purpose.
> In SQL 2000 this would cause queries against the view to be sorted. But
> this behavior was never guaranteed, and it doesn't always happen in 2005.
> David
>
>
I'm working for a hospital and for this job, I created two views using the
server aliases (linked servers).
Both these views are working correctly.
The design of the first view is:
SELECT TOP 100 PERCENT UNID AS ID, SPECIALTY_CODE AS CODE,
SPECIALTY_DESCRIPTION AS NAME
FROM ddsqlGIMS.GIMS.dbo.TBL_SPECIALTY TBL_SPECIALTY_1
ORDER BY SPECIALTY_DESCRIPTION
And for the second view is:
SELECT TOP 100 PERCENT CLINICIAN_ID AS ID, NAME, CLINICIAN_SPEC_CODE AS
SPECIALTY_CODE
FROM ddsqlGIMS.GIMS.dbo.TBL_CLINICIANS TBL_CLINICIANS_1
WHERE (GMC_NO IS NOT NULL) AND (ACTIVE_FLAG = 'Y')
ORDER BY NAME
The problem appaers when I try to join both these views with, for example,
this query:
select c.ID
from VW_CONSULTANTS c
left outer join VW_SPECIALTIES s
on c.SPECIALTY_CODE=s.CODE
I have these error messages:
Server: Msg 8180, Level 16, State 1, Line 1
Statement(s) could not be prepared.
Server: Msg 156, Level 15, State 1, Line 1
Incorrect syntax near the keyword 'ORDER'.
Server: Msg 1033, Level 15, State 1, Line 1
The ORDER BY clause is invalid in views, inline functions, derived tables,
and subqueries, unless TOP is also specified.
For me, the problem is because we try to join two views using server aliases
and the sql server is not successfull in creating the temporary table to put
the results of my select...
But I don't know what I have to do to fix the problem.
Can you help me please?
StF"StF" <StF@.discussions.microsoft.com> wrote in message
news:760671EB-8EC8-4464-8972-D570E0FB2F86@.microsoft.com...
> Hello everybody,
> I'm working for a hospital and for this job, I created two views using the
> server aliases (linked servers).
> Both these views are working correctly.
> The design of the first view is:
> SELECT TOP 100 PERCENT UNID AS ID, SPECIALTY_CODE AS CODE,
> SPECIALTY_DESCRIPTION AS NAME
> FROM ddsqlGIMS.GIMS.dbo.TBL_SPECIALTY TBL_SPECIALTY_1
> ORDER BY SPECIALTY_DESCRIPTION
> And for the second view is:
> SELECT TOP 100 PERCENT CLINICIAN_ID AS ID, NAME, CLINICIAN_SPEC_CODE
> AS
> SPECIALTY_CODE
> FROM ddsqlGIMS.GIMS.dbo.TBL_CLINICIANS TBL_CLINICIANS_1
> WHERE (GMC_NO IS NOT NULL) AND (ACTIVE_FLAG = 'Y')
> ORDER BY NAME
> The problem appaers when I try to join both these views with, for example,
> this query:
> select c.ID
> from VW_CONSULTANTS c
> left outer join VW_SPECIALTIES s
> on c.SPECIALTY_CODE=s.CODE
>
I don't know exactly what's happening, but I know how to fix it.
Don't use TOP 100 PERCENT in a view. It serves absolutely no purpose.
In SQL 2000 this would cause queries against the view to be sorted. But
this behavior was never guaranteed, and it doesn't always happen in 2005.
David|||Thank you very much.
In fact, we use SQL Server 2000 and that's why I used 'TOP 100 PERCENT'.
So, I removed this thing and the 'ORDER BY' and now my select is working.
Thank you again.
StF
"David Browne" wrote:
> "StF" <StF@.discussions.microsoft.com> wrote in message
> news:760671EB-8EC8-4464-8972-D570E0FB2F86@.microsoft.com...
> > Hello everybody,
> >
> > I'm working for a hospital and for this job, I created two views using the
> > server aliases (linked servers).
> > Both these views are working correctly.
> >
> > The design of the first view is:
> > SELECT TOP 100 PERCENT UNID AS ID, SPECIALTY_CODE AS CODE,
> > SPECIALTY_DESCRIPTION AS NAME
> > FROM ddsqlGIMS.GIMS.dbo.TBL_SPECIALTY TBL_SPECIALTY_1
> > ORDER BY SPECIALTY_DESCRIPTION
> >
> > And for the second view is:
> > SELECT TOP 100 PERCENT CLINICIAN_ID AS ID, NAME, CLINICIAN_SPEC_CODE
> > AS
> > SPECIALTY_CODE
> > FROM ddsqlGIMS.GIMS.dbo.TBL_CLINICIANS TBL_CLINICIANS_1
> > WHERE (GMC_NO IS NOT NULL) AND (ACTIVE_FLAG = 'Y')
> > ORDER BY NAME
> >
> > The problem appaers when I try to join both these views with, for example,
> > this query:
> > select c.ID
> > from VW_CONSULTANTS c
> > left outer join VW_SPECIALTIES s
> > on c.SPECIALTY_CODE=s.CODE
> >
> I don't know exactly what's happening, but I know how to fix it.
> Don't use TOP 100 PERCENT in a view. It serves absolutely no purpose.
> In SQL 2000 this would cause queries against the view to be sorted. But
> this behavior was never guaranteed, and it doesn't always happen in 2005.
> David
>
>
join two different databases where they r in different servers
i am fresher i want to know write one query where i want to select two tables from two different databases that are in different servers.
eg : it is first server details
sqlserver1 -servername
EmployeDet -Database Name
Emp_Mas - table name
colums - empno, empname,.....
it is second server details
sqlserver2 -servername
IMS- Database Name
IMSTable - table name
Colums- empno,locid,extno......
by combining above two databases i want details please help me in this issue it is urgent
You can do that using linked servers. Books online has quite a bit of
information about creating and using a linked server.
----
Need SQL Server Examples check out my website at
http://www.geocities.com/sqlserverexamples
"Naga vinay kumar .K" <anonymous@.discussions.microsoft.com> wrote in message
news:8F753D93-EB6A-4436-977D-436D92EE99B8@.microsoft.com...
> i am fresher i want to know write one query where i want to select two
tables from two different databases that are in different servers.
> eg : it is first server details
> sqlserver1 -servername
> EmployeDet -Database Name
> Emp_Mas - table name
> colums - empno, empname,.....
> it is second server details
> sqlserver2 -servername
> IMS- Database Name
> IMSTable - table name
> Colums- empno,locid,extno......
> by combining above two databases i want details please help me in this
issue it is urgent
>
>
eg : it is first server details
sqlserver1 -servername
EmployeDet -Database Name
Emp_Mas - table name
colums - empno, empname,.....
it is second server details
sqlserver2 -servername
IMS- Database Name
IMSTable - table name
Colums- empno,locid,extno......
by combining above two databases i want details please help me in this issue it is urgent
You can do that using linked servers. Books online has quite a bit of
information about creating and using a linked server.
----
Need SQL Server Examples check out my website at
http://www.geocities.com/sqlserverexamples
"Naga vinay kumar .K" <anonymous@.discussions.microsoft.com> wrote in message
news:8F753D93-EB6A-4436-977D-436D92EE99B8@.microsoft.com...
> i am fresher i want to know write one query where i want to select two
tables from two different databases that are in different servers.
> eg : it is first server details
> sqlserver1 -servername
> EmployeDet -Database Name
> Emp_Mas - table name
> colums - empno, empname,.....
> it is second server details
> sqlserver2 -servername
> IMS- Database Name
> IMSTable - table name
> Colums- empno,locid,extno......
> by combining above two databases i want details please help me in this
issue it is urgent
>
>
join two different databases where they r in different servers
i am fresher i want to know write one query where i want to select two table
s from two different databases that are in different servers.
eg : it is first server details
sqlserver1 -servername
EmployeDet -Database Name
Emp_Mas - table name
colums - empno, empname,.....
it is second server details
sqlserver2 -servername
IMS- Database Name
IMSTable - table name
Colums- empno,locid,extno......
by combining above two databases i want details please help me in this issue
it is urgentYou can do that using linked servers. Books online has quite a bit of
information about creating and using a linked server.
----
----
--
Need SQL Server Examples check out my website at
http://www.geocities.com/sqlserverexamples
"Naga vinay kumar .K" <anonymous@.discussions.microsoft.com> wrote in message
news:8F753D93-EB6A-4436-977D-436D92EE99B8@.microsoft.com...
> i am fresher i want to know write one query where i want to select two
tables from two different databases that are in different servers.
> eg : it is first server details
> sqlserver1 -servername
> EmployeDet -Database Name
> Emp_Mas - table name
> colums - empno, empname,.....
> it is second server details
> sqlserver2 -servername
> IMS- Database Name
> IMSTable - table name
> Colums- empno,locid,extno......
> by combining above two databases i want details please help me in this
issue it is urgent
>
>
s from two different databases that are in different servers.
eg : it is first server details
sqlserver1 -servername
EmployeDet -Database Name
Emp_Mas - table name
colums - empno, empname,.....
it is second server details
sqlserver2 -servername
IMS- Database Name
IMSTable - table name
Colums- empno,locid,extno......
by combining above two databases i want details please help me in this issue
it is urgentYou can do that using linked servers. Books online has quite a bit of
information about creating and using a linked server.
----
----
--
Need SQL Server Examples check out my website at
http://www.geocities.com/sqlserverexamples
"Naga vinay kumar .K" <anonymous@.discussions.microsoft.com> wrote in message
news:8F753D93-EB6A-4436-977D-436D92EE99B8@.microsoft.com...
> i am fresher i want to know write one query where i want to select two
tables from two different databases that are in different servers.
> eg : it is first server details
> sqlserver1 -servername
> EmployeDet -Database Name
> Emp_Mas - table name
> colums - empno, empname,.....
> it is second server details
> sqlserver2 -servername
> IMS- Database Name
> IMSTable - table name
> Colums- empno,locid,extno......
> by combining above two databases i want details please help me in this
issue it is urgent
>
>
join two different databases where they r in different servers
i am fresher i want to know write one query where i want to select two tables from two different databases that are in different servers
eg : it is first server detail
sqlserver1 -servernam
EmployeDet -Database Nam
Emp_Mas - table nam
colums - empno, empname,....
it is second server detail
sqlserver2 -servernam
IMS- Database Nam
IMSTable - table nam
Colums- empno,locid,extno.....
by combining above two databases i want details please help me in this issue it is urgenYou can do that using linked servers. Books online has quite a bit of
information about creating and using a linked server.
--
----
----
--
Need SQL Server Examples check out my website at
http://www.geocities.com/sqlserverexamples
"Naga vinay kumar .K" <anonymous@.discussions.microsoft.com> wrote in message
news:8F753D93-EB6A-4436-977D-436D92EE99B8@.microsoft.com...
> i am fresher i want to know write one query where i want to select two
tables from two different databases that are in different servers.
> eg : it is first server details
> sqlserver1 -servername
> EmployeDet -Database Name
> Emp_Mas - table name
> colums - empno, empname,.....
> it is second server details
> sqlserver2 -servername
> IMS- Database Name
> IMSTable - table name
> Colums- empno,locid,extno......
> by combining above two databases i want details please help me in this
issue it is urgent
>
>
eg : it is first server detail
sqlserver1 -servernam
EmployeDet -Database Nam
Emp_Mas - table nam
colums - empno, empname,....
it is second server detail
sqlserver2 -servernam
IMS- Database Nam
IMSTable - table nam
Colums- empno,locid,extno.....
by combining above two databases i want details please help me in this issue it is urgenYou can do that using linked servers. Books online has quite a bit of
information about creating and using a linked server.
--
----
----
--
Need SQL Server Examples check out my website at
http://www.geocities.com/sqlserverexamples
"Naga vinay kumar .K" <anonymous@.discussions.microsoft.com> wrote in message
news:8F753D93-EB6A-4436-977D-436D92EE99B8@.microsoft.com...
> i am fresher i want to know write one query where i want to select two
tables from two different databases that are in different servers.
> eg : it is first server details
> sqlserver1 -servername
> EmployeDet -Database Name
> Emp_Mas - table name
> colums - empno, empname,.....
> it is second server details
> sqlserver2 -servername
> IMS- Database Name
> IMSTable - table name
> Colums- empno,locid,extno......
> by combining above two databases i want details please help me in this
issue it is urgent
>
>
Wednesday, March 7, 2012
join SQL server into domain
Hi all,
I have 3 W2K3 servers running in WORKGROUP: one SQL2K5 running as the
backend database server; one Sharepoint server; one SQL Report Server web
server.
I'm going to join these 3 servers into AD domain, will it cause any problem?
Will it break the connection between the SQL server and the other 2 servers?
Anyone has experience on this? Thanks!
MliHi
If you rename the server then you will need to
http://msdn2.microsoft.com/en-us/library/ms143799.aspx and also change any
connections strings to the new name. Logins from the old workgroup may need
removing and new ones added for the domain. Service accounts may require
changing and orphaned users may need to be resolved
http://support.microsoft.com/kb/314546. If you create any new users they wil
l
need to have permissions added.
John
"MLi" wrote:
> Hi all,
> I have 3 W2K3 servers running in WORKGROUP: one SQL2K5 running as the
> backend database server; one Sharepoint server; one SQL Report Server web
> server.
> I'm going to join these 3 servers into AD domain, will it cause any proble
m?
> Will it break the connection between the SQL server and the other 2 server
s?
> Anyone has experience on this? Thanks!
>
> Mli
>
>
>|||Thanks John.
I'm not gonna change the server name, however because it will be joined a
domain, the DNS name will be changed. Is there any concern?
MLi
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:26F04787-0DB9-4C8C-8D60-1EA65E52F8E7@.microsoft.com...[vbcol=seagreen]
> Hi
> If you rename the server then you will need to
> http://msdn2.microsoft.com/en-us/library/ms143799.aspx and also change any
> connections strings to the new name. Logins from the old workgroup may
> need
> removing and new ones added for the domain. Service accounts may require
> changing and orphaned users may need to be resolved
> http://support.microsoft.com/kb/314546. If you create any new users they
> will
> need to have permissions added.
> John
> "MLi" wrote:
>|||Hi
The name of the instance will still be the name of the old servername,
SELECT @.@.SERVERNAME will still show the old one. That is why you need to dro
p
it and create the new one.
John
"MLi" wrote:
> Thanks John.
> I'm not gonna change the server name, however because it will be joined a
> domain, the DNS name will be changed. Is there any concern?
>
> MLi
>
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:26F04787-0DB9-4C8C-8D60-1EA65E52F8E7@.microsoft.com...
>
>
I have 3 W2K3 servers running in WORKGROUP: one SQL2K5 running as the
backend database server; one Sharepoint server; one SQL Report Server web
server.
I'm going to join these 3 servers into AD domain, will it cause any problem?
Will it break the connection between the SQL server and the other 2 servers?
Anyone has experience on this? Thanks!
MliHi
If you rename the server then you will need to
http://msdn2.microsoft.com/en-us/library/ms143799.aspx and also change any
connections strings to the new name. Logins from the old workgroup may need
removing and new ones added for the domain. Service accounts may require
changing and orphaned users may need to be resolved
http://support.microsoft.com/kb/314546. If you create any new users they wil
l
need to have permissions added.
John
"MLi" wrote:
> Hi all,
> I have 3 W2K3 servers running in WORKGROUP: one SQL2K5 running as the
> backend database server; one Sharepoint server; one SQL Report Server web
> server.
> I'm going to join these 3 servers into AD domain, will it cause any proble
m?
> Will it break the connection between the SQL server and the other 2 server
s?
> Anyone has experience on this? Thanks!
>
> Mli
>
>
>|||Thanks John.
I'm not gonna change the server name, however because it will be joined a
domain, the DNS name will be changed. Is there any concern?
MLi
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:26F04787-0DB9-4C8C-8D60-1EA65E52F8E7@.microsoft.com...[vbcol=seagreen]
> Hi
> If you rename the server then you will need to
> http://msdn2.microsoft.com/en-us/library/ms143799.aspx and also change any
> connections strings to the new name. Logins from the old workgroup may
> need
> removing and new ones added for the domain. Service accounts may require
> changing and orphaned users may need to be resolved
> http://support.microsoft.com/kb/314546. If you create any new users they
> will
> need to have permissions added.
> John
> "MLi" wrote:
>|||Hi
The name of the instance will still be the name of the old servername,
SELECT @.@.SERVERNAME will still show the old one. That is why you need to dro
p
it and create the new one.
John
"MLi" wrote:
> Thanks John.
> I'm not gonna change the server name, however because it will be joined a
> domain, the DNS name will be changed. Is there any concern?
>
> MLi
>
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:26F04787-0DB9-4C8C-8D60-1EA65E52F8E7@.microsoft.com...
>
>
join SQL server into domain
Hi all,
I have 3 W2K3 servers running in WORKGROUP: one SQL2K5 running as the
backend database server; one Sharepoint server; one SQL Report Server web
server.
I'm going to join these 3 servers into AD domain, will it cause any problem?
Will it break the connection between the SQL server and the other 2 servers?
Anyone has experience on this? Thanks!
MliHi
If you rename the server then you will need to
http://msdn2.microsoft.com/en-us/library/ms143799.aspx and also change any
connections strings to the new name. Logins from the old workgroup may need
removing and new ones added for the domain. Service accounts may require
changing and orphaned users may need to be resolved
http://support.microsoft.com/kb/314546. If you create any new users they will
need to have permissions added.
John
"MLi" wrote:
> Hi all,
> I have 3 W2K3 servers running in WORKGROUP: one SQL2K5 running as the
> backend database server; one Sharepoint server; one SQL Report Server web
> server.
> I'm going to join these 3 servers into AD domain, will it cause any problem?
> Will it break the connection between the SQL server and the other 2 servers?
> Anyone has experience on this? Thanks!
>
> Mli
>
>
>|||Thanks John.
I'm not gonna change the server name, however because it will be joined a
domain, the DNS name will be changed. Is there any concern?
MLi
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:26F04787-0DB9-4C8C-8D60-1EA65E52F8E7@.microsoft.com...
> Hi
> If you rename the server then you will need to
> http://msdn2.microsoft.com/en-us/library/ms143799.aspx and also change any
> connections strings to the new name. Logins from the old workgroup may
> need
> removing and new ones added for the domain. Service accounts may require
> changing and orphaned users may need to be resolved
> http://support.microsoft.com/kb/314546. If you create any new users they
> will
> need to have permissions added.
> John
> "MLi" wrote:
>> Hi all,
>> I have 3 W2K3 servers running in WORKGROUP: one SQL2K5 running as the
>> backend database server; one Sharepoint server; one SQL Report Server web
>> server.
>> I'm going to join these 3 servers into AD domain, will it cause any
>> problem?
>> Will it break the connection between the SQL server and the other 2
>> servers?
>> Anyone has experience on this? Thanks!
>>
>> Mli
>>
>>|||Hi
The name of the instance will still be the name of the old servername,
SELECT @.@.SERVERNAME will still show the old one. That is why you need to drop
it and create the new one.
John
"MLi" wrote:
> Thanks John.
> I'm not gonna change the server name, however because it will be joined a
> domain, the DNS name will be changed. Is there any concern?
>
> MLi
>
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:26F04787-0DB9-4C8C-8D60-1EA65E52F8E7@.microsoft.com...
> > Hi
> >
> > If you rename the server then you will need to
> > http://msdn2.microsoft.com/en-us/library/ms143799.aspx and also change any
> > connections strings to the new name. Logins from the old workgroup may
> > need
> > removing and new ones added for the domain. Service accounts may require
> > changing and orphaned users may need to be resolved
> > http://support.microsoft.com/kb/314546. If you create any new users they
> > will
> > need to have permissions added.
> >
> > John
> >
> > "MLi" wrote:
> >
> >> Hi all,
> >>
> >> I have 3 W2K3 servers running in WORKGROUP: one SQL2K5 running as the
> >> backend database server; one Sharepoint server; one SQL Report Server web
> >> server.
> >>
> >> I'm going to join these 3 servers into AD domain, will it cause any
> >> problem?
> >> Will it break the connection between the SQL server and the other 2
> >> servers?
> >>
> >> Anyone has experience on this? Thanks!
> >>
> >>
> >> Mli
> >>
> >>
> >>
> >>
> >>
>
>
I have 3 W2K3 servers running in WORKGROUP: one SQL2K5 running as the
backend database server; one Sharepoint server; one SQL Report Server web
server.
I'm going to join these 3 servers into AD domain, will it cause any problem?
Will it break the connection between the SQL server and the other 2 servers?
Anyone has experience on this? Thanks!
MliHi
If you rename the server then you will need to
http://msdn2.microsoft.com/en-us/library/ms143799.aspx and also change any
connections strings to the new name. Logins from the old workgroup may need
removing and new ones added for the domain. Service accounts may require
changing and orphaned users may need to be resolved
http://support.microsoft.com/kb/314546. If you create any new users they will
need to have permissions added.
John
"MLi" wrote:
> Hi all,
> I have 3 W2K3 servers running in WORKGROUP: one SQL2K5 running as the
> backend database server; one Sharepoint server; one SQL Report Server web
> server.
> I'm going to join these 3 servers into AD domain, will it cause any problem?
> Will it break the connection between the SQL server and the other 2 servers?
> Anyone has experience on this? Thanks!
>
> Mli
>
>
>|||Thanks John.
I'm not gonna change the server name, however because it will be joined a
domain, the DNS name will be changed. Is there any concern?
MLi
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:26F04787-0DB9-4C8C-8D60-1EA65E52F8E7@.microsoft.com...
> Hi
> If you rename the server then you will need to
> http://msdn2.microsoft.com/en-us/library/ms143799.aspx and also change any
> connections strings to the new name. Logins from the old workgroup may
> need
> removing and new ones added for the domain. Service accounts may require
> changing and orphaned users may need to be resolved
> http://support.microsoft.com/kb/314546. If you create any new users they
> will
> need to have permissions added.
> John
> "MLi" wrote:
>> Hi all,
>> I have 3 W2K3 servers running in WORKGROUP: one SQL2K5 running as the
>> backend database server; one Sharepoint server; one SQL Report Server web
>> server.
>> I'm going to join these 3 servers into AD domain, will it cause any
>> problem?
>> Will it break the connection between the SQL server and the other 2
>> servers?
>> Anyone has experience on this? Thanks!
>>
>> Mli
>>
>>|||Hi
The name of the instance will still be the name of the old servername,
SELECT @.@.SERVERNAME will still show the old one. That is why you need to drop
it and create the new one.
John
"MLi" wrote:
> Thanks John.
> I'm not gonna change the server name, however because it will be joined a
> domain, the DNS name will be changed. Is there any concern?
>
> MLi
>
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:26F04787-0DB9-4C8C-8D60-1EA65E52F8E7@.microsoft.com...
> > Hi
> >
> > If you rename the server then you will need to
> > http://msdn2.microsoft.com/en-us/library/ms143799.aspx and also change any
> > connections strings to the new name. Logins from the old workgroup may
> > need
> > removing and new ones added for the domain. Service accounts may require
> > changing and orphaned users may need to be resolved
> > http://support.microsoft.com/kb/314546. If you create any new users they
> > will
> > need to have permissions added.
> >
> > John
> >
> > "MLi" wrote:
> >
> >> Hi all,
> >>
> >> I have 3 W2K3 servers running in WORKGROUP: one SQL2K5 running as the
> >> backend database server; one Sharepoint server; one SQL Report Server web
> >> server.
> >>
> >> I'm going to join these 3 servers into AD domain, will it cause any
> >> problem?
> >> Will it break the connection between the SQL server and the other 2
> >> servers?
> >>
> >> Anyone has experience on this? Thanks!
> >>
> >>
> >> Mli
> >>
> >>
> >>
> >>
> >>
>
>
Subscribe to:
Posts (Atom)