Can we change the name of the instance ..

Can we change the name of the instance (SomeSQLInstance1, Some SQLInstance2) to be "SomeSQLStdInstance" while upgrading to SQL 2005 from MSDE 2k or SQL 2000?

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

can view reports created in RS after upgrading to RS sp1?

Hi,
My server is currently running Reporting Services. I want to upgrade it
to reporting services sp1 or sp2. I wanna know after upgrading it to
sp1, will I will be able to view my older reports which is created
using reporting services?No problem. I suggest sp2. Also, upgrade your designer as well.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"sheerin" <susheelkaur@.gmail.com> wrote in message
news:1141189981.337655.34260@.e56g2000cwe.googlegroups.com...
> Hi,
> My server is currently running Reporting Services. I want to upgrade it
> to reporting services sp1 or sp2. I wanna know after upgrading it to
> sp1, will I will be able to view my older reports which is created
> using reporting services?
>

Can the use of Shrinkfile break the Transaction Log chain?

My Log Shipping process has been up and running fine for about 6 months now.
Then as part of the preparation for upgrading the front end application for
the log shipped database, my partner DBA thought he would help the backup
speed by running a SHRINKFILE over the database files.
It was on or about this time that log shipping stopped working and reported
errors just like the ones you get when the transaction log has been
truncated. Basically it thinks the T Log chain has been broken.
Can SHRINKFILE break the chain? I thought it only compacted the unused file
space?
In my tests log shipping was not sensitive to shrinkfile statements. Perhaps
something else has gone wrong.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"GRP" <GRP@.discussions.microsoft.com> wrote in message
news:BD8BC1B6-FD32-43C2-B34E-7CA0397CAC35@.microsoft.com...
> My Log Shipping process has been up and running fine for about 6 months
now.
> Then as part of the preparation for upgrading the front end application
for
> the log shipped database, my partner DBA thought he would help the backup
> speed by running a SHRINKFILE over the database files.
> It was on or about this time that log shipping stopped working and
reported
> errors just like the ones you get when the transaction log has been
> truncated. Basically it thinks the T Log chain has been broken.
> Can SHRINKFILE break the chain? I thought it only compacted the unused
file
> space?
|||Hilary, thanks for taking the time to test this out. The only other
explanation I can think of is that the other DBA truncated the log prior to
the shrinkfile.
"Hilary Cotter" wrote:

> In my tests log shipping was not sensitive to shrinkfile statements. Perhaps
> something else has gone wrong.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "GRP" <GRP@.discussions.microsoft.com> wrote in message
> news:BD8BC1B6-FD32-43C2-B34E-7CA0397CAC35@.microsoft.com...
> now.
> for
> reported
> file
>
>

Can SRS 2000 rdl files be published to and run on sql server 2005?

We're planning on upgrading from sql server 2000 to 2005 and we're hoping
that SRS 2000 .rdl files will run on sql server 2005.
Can anyone confirm if this is the case or not.
Thanks in advance for your help.Yes. However, when I upgraded I had some small weird problems. I then opened
up the rdl files with the RS 2005 designer, converted to RS 2005 and
re-deployed and the problems went away. Nothing major and we were able to
function but obnoxious. I can't tell you exactly what would occur, its been
awhile since I upgraded.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Sherman In Denver" <sherman@.newsgroup.nospam> wrote in message
news:3524E97D-9C2A-4D56-8A7E-2FE28E427A3B@.microsoft.com...
> We're planning on upgrading from sql server 2000 to 2005 and we're hoping
> that SRS 2000 .rdl files will run on sql server 2005.
> Can anyone confirm if this is the case or not.
> Thanks in advance for your help.
>|||Hello Sherman,
I agree with Bruce. There are some changes in the RDL file format between
RS2000 and RS2005, I would suggest you open the SSRS 2000 RDL file in SQL
2005 BI Studio's report designer, it will help convert your RDL to RS 2005
format.
Also, if you still want to use RS2000 reports on SQL Server 2000 later, I
suggest you make an backup for the RS 2000 RDL files.
In addition, you can search for some former threads discussing on RS
2000--> RS 2005 report converting if you meet any particular converting
issues.
Sincerely,
Steven Cheng
Microsoft MSDN Online Support Lead
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.|||Hello,
How are you doing on this issue. Does Bruce and Steven's reply and
suggestion helps you some? If there is still anything we can help, please
feel free to post in the newsgroup.
Thank you for using our MSDN Managed Newsgroup Support Service!
Sincerely,
Luke Zhang
Microsoft Online Community Support
This posting is provided "AS IS" with no warranties, and confers no rights.

Can SQL Server 2005 Express and MSDE CoExist?

I read in the installation requirements document for SQL Server 2005 Express the section on upgrading MSDE to SQL Server 2005 Express. The section indicated that if MSDE is installed via an application installation, that application will have to be uninstalled to remove MSDE. This leads to my question.

The small application I'm looking into developing will require SQL Server 2005 Express. What if a customer is using an application that installed MSDE? Can the two products coexist without problems?

Thanks!!

hi,

yes, MSDE 2000 and SQLExpress can coexists...

SQLExpress installation will upgrade the installed COM based binaries (SQL-DMO) to SQL Server 2005 level, but they have been tested to be retro-compatible and I'm personally not aware of troubles in this area..

regards

Can SQL Server 2005 Evaluation be used to upgrade a system?

I have multiple development SQL Servers running Enterprise edition that I want to upgrade for application testing before upgrading our production system. All of the servers meet the hardware and software requirements for SQL Server 2005 Enterprise edition. However, when I try to install to use the SQL Server 2005 Evaluation Edition to upgrade the servers in place, I get the blocked upgrade message:

Name: Microsoft SQL Server 2000 Reason: Your upgrade is blocked. For more information about upgrade support, see the "Version and Edition Upgrades" and "Hardware and Software Requirements" topics in SQL Server 2005 Setup Help or SQL Server 2005 Books Online. Edition check: Your upgrade is blocked because of edition upgrade rules. For more information about edition upgrades, see the Version and Edition Upgrades topic in SQL Server 2005 Setup Help or SQL Server 2005 Books Online.

Can the Evaluation Edition be used to upgrade these servers or do you need the full blown version?

thanks

Sorry, upgrades are prohibited *to* the Eval edition.|||I am getting this error now myself and I don't know why. I installed the trial SQL Server Express for my boss. He then asked if I would install the trial SQL Server 2005 becuase it has more capabilities he would like to try out. So I installed 2005. He noticed that there was no management studio installed and needed. So I uninstalled it and am trying to reinstall it and am getting this error. I haven't even used the software yet! I don't know what to do!|||

I was able to continue the installation but just before I click OK to install, I see this in a window

The following components that you selected will not be changed:

Client Components

that might be why I had my original problem. That problem was the Management Studio was never installed which prompted me to reinstall the system alltogether thinking I must have not checked that installation option.

Ahh!!!

Can SQL Server 2005 Evaluation be used to upgrade a system?

I have multiple development SQL Servers running Enterprise edition that I want to upgrade for application testing before upgrading our production system. All of the servers meet the hardware and software requirements for SQL Server 2005 Enterprise edition. However, when I try to install to use the SQL Server 2005 Evaluation Edition to upgrade the servers in place, I get the blocked upgrade message:

Name: Microsoft SQL Server 2000

Reason: Your upgrade is blocked. For more information about upgrade support, see the "Version and Edition Upgrades" and "Hardware and Software Requirements" topics in SQL Server 2005 Setup Help or SQL Server 2005 Books Online.

Edition check:

Your upgrade is blocked because of edition upgrade rules. For more information about edition upgrades, see the Version and Edition Upgrades topic in SQL Server 2005 Setup Help or SQL Server 2005 Books Online.

Can the Evaluation Edition be used to upgrade these servers or do you need the full blown version?

thanks

Sorry, upgrades are prohibited *to* the Eval edition.|||I am getting this error now myself and I don't know why. I installed the trial SQL Server Express for my boss. He then asked if I would install the trial SQL Server 2005 becuase it has more capabilities he would like to try out. So I installed 2005. He noticed that there was no management studio installed and needed. So I uninstalled it and am trying to reinstall it and am getting this error. I haven't even used the software yet! I don't know what to do!|||

I was able to continue the installation but just before I click OK to install, I see this in a window

The following components that you selected will not be changed:

Client Components

that might be why I had my original problem. That problem was the Management Studio was never installed which prompted me to reinstall the system alltogether thinking I must have not checked that installation option.

Ahh!!!