Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
chriskhan2000
Aged Yak Warrior
544 Posts |
 Posted - 2005-09-15 : 12:52:19
|
| I'm running into issues where my reports doesn't seem to recognize the different server name change within my datasource. We have recently move our database to a new server and the server name is not the same as the old one. I thought that if I go and change the datasource to point to that server it should be fine, but i'm getting error saying that password is incorrect for sa.Any ideas? |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2005-09-15 : 13:11:38
|
| Why are you using the sa account!!!?Where is it breaking from? Report Server, Report Manager, Visual Studio? Have you tried your password in Query Analyzer? Tara |
 |
|
|
jhermiz
3564 Posts |
Posted - 2005-09-17 : 05:55:49
|
Chris,Don't use the sa account since it basically has access to virtually everything. I know you may be saying to yourself, "but who cares, only I touch the software in the company I work for". But it is best to be safe rather than sorry. Create specific users for specific databases. Or create a specific user to run the reports and grant access to the stored procedures or data objects you need to run these reports. Setting the user as SA means you have all the freedom in the world to create / delete / and run things that you may not need to be running, especially in a reporting environment.Jon
Keeping the web experience alive -- [url]http://www.web-impulse.com[/url]Imperfection living for perfection -- [url]http://jhermiz.blogspot.com/[/url] |
|
|
|
chriskhan2000
Aged Yak Warrior
544 Posts |
Posted - 2005-09-23 : 07:45:13
|
| You both are correct on this. We do have specific users created for specific databases with specific rights to the databases. There's 1 report that only uses the ODBC with sa account, and my boss is the only person to have access to this report. I'm not sure what is his reason for this but he wants sa for this ODBC and since we did the database move the ODBC needs to see the new server. I got it to work now because I did not see that the ODBC is buried deep within several subfolders. Went in and change the server to the new one and it works fine. |
|
|
|
|
|
|
Server name change issue?