Thanks in Advance,
Ram
You can always execute sp_helpfile in a database to find the files for that database.
Or select * from sys.database_files
-Sue
Thanks in Advance,
Ram
You can always execute sp_helpfile in a database to find the files for that database.
Or select * from sys.database_files
-Sue
Yes. You can change the name of an instance as long as the server is not clustered. For more information, visit the following Microsoft Developer Network (MSDN) Web site:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/instsql/in_afterinstall_5r8f.asp
Thanks
|||hi,
Rubal Jain wrote:
Yes. You can change the name of an instance as long as the server is not clustered. For more information, visit the following Microsoft Developer Network (MSDN) Web site:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/instsql/in_afterinstall_5r8f.asp
the feature you reported is only able to resync the server name to a SQL Server instance and not to just "rename" an installed instance..
if you installed a local named instance of SQLExpress, usually named (Local)\SQLExpress, you can not rename it to (Local)\AndreaSQLX or the like...
to "rename" an instance you have to uninstall it and reinstall it..
regards
I was wondering SQL Server 2005 Reporting Services can run against/on a SQL Server 2000 database/instance?
Thanks,
Michael
Yes, for both metadata (the Report Server database) as well as report data.|||Is there anything that I should know about when installing the SQL Server 2005 Reporting services? Is there any special requirements? Are there any special requirements when upgrading from SQL Server 2000 Reporting Services to SQL Server 2005 Reporting Services?
I do appreciate the help and advice. Google unfortunately has not turned up any answers for me.
Thanks,
Michael
|||TechNet did a support webcast on Upgrading SQL Server 2005 Reporting Services couple of days ago. You can download it fromhttp://support.microsoft.com/default.aspx?scid=kb;en-us;913930
|||Thank you so much. I appreciate the help. This solves my problem.
Michael
hi,
SQL Server 2000 (including MSDE) and SQL Server 2005 (including SQLExpress) cna be installed "side by side"...
you can install up to 16 different instances per box, and each instance will maintain it's own binaries and registry settings separated from all other instances.. even at different service pack levels..
obviously you have not to mismatch instance's names.. only 1 instance per box can be the "default" instance, known as "ComputerName" or "." or "(Local)" (the last 2 only for local connections), where all the other instances have to be "named" instances, known as "ComputerName\InstanceName" or ".\InstanceName" or "(Local)\InstanceName" ... further info at http://msdn2.microsoft.com/en-us/library/ms143547.aspx
a little "note" should be mentioned about shared components.. this binaries are actually shared among all instances of the same code base.. so all 2000 related shared binaries will be shared among all 2000 instances, where 2005 shared components will be shared with all 2005 instances, at the higher service pack level..
another "side note".. and this is COM related.. COM components do not allow "side by side" implementation, so that SQL Server 2005 installs some of them at the 2005 edition level.. and SQL Server 2000 will "inherit" those components.. think about SQL-DMO and the like, but you should not be interested with that as 2005 versions are downwards compatible...
regards
|||Thanks a lot!
I had a big problem on connecting sqlserver remotely from other machines on the network .....
From any computer in the network i wanna to register the instance of the sqlserver from the enterprise manager ..... the server instance doesn't appear within the available sqlserver list (the servername which equal to my machine is the only one that appear) ..... when i manualy write the servername\alias manually and i choose the connection type and then i write sqlserver username and password and then finish he give a message to me that access denied or sql server doesn't exist ... !!
by the way from the local machine i registered the local instance of sqlserver successfully and successfully i access the Databases .....
To be noted:
I previously uninstalled this alias and i then i reinstalled it again with the same name and i attached the previously exists Databes.
in the same time i installed on the same machine sqlserver 2005 connectivity clients not the server itself.
Why are you using aliases? Do select @.@.servername, and tell me if this is the exact name you're trying to connect to via enterprise manager.|||
thank you for trying to help me,
I am using an alias from a long time and it was working good until i uninstalled the server and installed it agian .......
when i make "select @.@.servername" it return back "magedsalah\maged" and as i told before it works well on the local machine where i can connect with the enterprise manager to magedsalah\maged without any problems ......
the problem when anybody wanna to register magedsalah\maged in the enterprise manager of another computer the magedsalah\maged doesn't appear in the servers list what appear is magedsalah and it can't be registered and sometimes and some there is nothing appear at all.....
for further details plz refer to original message in the thread.....
thanks
|||Did you ever figure out the solution to this, I'm having the exact same problem, it occured after I installed Sql 2005, and now i'm using named instances.|||Hi,
After i trapped in solving this problem ..... i removed the existing sql server 2000 where i use the alias and then i installed it again without alias (the default case in setup) ..... then i reattached my databases ......... and it works fine now
|||I ended up doing the same thing too, and mine works too now. There must be a trick to making it work with alias'/instance names too though, oh well.
Thanks
