Showing posts with label upgrade. Show all posts
Showing posts with label upgrade. Show all posts

Tuesday, March 27, 2012

Can not install July CTP with June CTP already installed

I was thinking the installing July CTP upon June CTP is like installing a service pack, but the set up tells me the upgrade was blocked.

Any one has any idea how to install July CTP on a server with June CTP installed already?

Do I have to back up all the databases and uninstall June CTP and do a installation of July CTP from scratch and restored all the databases or is there a way of upgrading to July CTP?

Any comments and inputs are highly appreciated.

Bo

Hi Bo,

We are currently not supporting a direct upgrade between the two CTPs. You should however be able to backup your database, uninstall the June CTP, install the July CTP and then attach your database. This should be the easiest route between the two CTPs.

Thank you,

Elisa Flasko

Program Manager, Data Programmability

|||

It worked for me, though it seems a little bit tedious.

Thanks a lot for your advice, Elisa.

sql

Sunday, March 11, 2012

Can Incremental Backup be done with Simple recovery Model?

For SQL2000 - Just wondering if the incremental backup requires transaction
logs.
We have a database upgrade process that performs a lot of updates. In order
to keep the transaction log from growing out of control - I would like to be
able to set the recovery model as "simple". I am hoping that I could do the
following:
1. Perform a full DB backup
2. Set the recovery model to Simple
3. Run the upgrade
4. Set the recovery model back to Full
5. Run an incremental backup
Does this sound reasonable? Should steps 4 and 5 be reversed?
Thanks in advance.
No, Incremental backups (which are called transaction log backups in SQL server) are based on the
transaction log. If you are missing log records in the transaction log, you wouldn't be able to
restore from the transaction log backups.
Consider differential backups, perhaps?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"TJT" <TJT@.nospam.com> wrote in message news:OWT5nJ%23eFHA.3808@.TK2MSFTNGP14.phx.gbl...
> For SQL2000 - Just wondering if the incremental backup requires transaction
> logs.
> We have a database upgrade process that performs a lot of updates. In order
> to keep the transaction log from growing out of control - I would like to be
> able to set the recovery model as "simple". I am hoping that I could do the
> following:
> 1. Perform a full DB backup
> 2. Set the recovery model to Simple
> 3. Run the upgrade
> 4. Set the recovery model back to Full
> 5. Run an incremental backup
> Does this sound reasonable? Should steps 4 and 5 be reversed?
> Thanks in advance.
>
|||"TJT" <TJT@.nospam.com> wrote in message
news:OWT5nJ#eFHA.3808@.TK2MSFTNGP14.phx.gbl...
> For SQL2000 - Just wondering if the incremental backup requires
transaction
> logs.
> We have a database upgrade process that performs a lot of updates. In
order
> to keep the transaction log from growing out of control - I would like to
be
> able to set the recovery model as "simple". I am hoping that I could do
the
> following:
> 1. Perform a full DB backup
> 2. Set the recovery model to Simple
> 3. Run the upgrade
> 4. Set the recovery model back to Full
> 5. Run an incremental backup
> Does this sound reasonable? Should steps 4 and 5 be reversed?
> Thanks in advance.
>
If this is a one-time upgrade, I would suggest the following...
1. Perform Full DB Backup
2. Set to Simple
3. Run upgrade
4. Perform Full DB Backup
5. Test your upgraded information. If all is OK
6. Set recovery back to full.
I'm not sure why you need the incrementals.
Rick Sawtell
MCT, MCSD, MCDBA
|||Hi Tibor,
Actually - I really meant to ask the question about Differential backups
(and not Incremental). I just had my terminology messed up.
So - would I be able to do this for Differential backups...
1. Perform a full DB backup
2. Set the recovery model to Simple
3. Run the upgrade
4. Set the recovery model back to Full
5. Run a differential backup
Thanks!
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:u4zfMN%23eFHA.3012@.tk2msftngp13.phx.gbl...
> No, Incremental backups (which are called transaction log backups in SQL
server) are based on the
> transaction log. If you are missing log records in the transaction log,
you wouldn't be able to
> restore from the transaction log backups.
> Consider differential backups, perhaps?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "TJT" <TJT@.nospam.com> wrote in message
news:OWT5nJ%23eFHA.3808@.TK2MSFTNGP14.phx.gbl...[vbcol=seagreen]
transaction[vbcol=seagreen]
order[vbcol=seagreen]
to be[vbcol=seagreen]
the
>
|||Hi Rick,
The database is rather large (90GB) and we are trying to minimize downtime.
This is why I was hoping to perform a differential backup.
If the database were small and downtime were not a problem - I would perform
another Full backup after the upgrade as you suggest.
Thanks,
Tom
"Rick Sawtell" <r_sawtell@.hotmail.com> wrote in message
news:uvuhVO%23eFHA.1448@.TK2MSFTNGP14.phx.gbl...[vbcol=seagreen]
> "TJT" <TJT@.nospam.com> wrote in message
> news:OWT5nJ#eFHA.3808@.TK2MSFTNGP14.phx.gbl...
> transaction
> order
to
> be
> the
> If this is a one-time upgrade, I would suggest the following...
> 1. Perform Full DB Backup
> 2. Set to Simple
> 3. Run upgrade
> 4. Perform Full DB Backup
> 5. Test your upgraded information. If all is OK
> 6. Set recovery back to full.
>
> I'm not sure why you need the incrementals.
> Rick Sawtell
> MCT, MCSD, MCDBA
>
>
|||Yes, that should work. Just test on a test server that the steps are fine first (possibly with less
data volume). Also, be aware that you have now broken your chains of log backups. The log backup
taken after this will not be able to apply after a log backup taken before all this. Only from the
last db backup.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"TJT" <TJT@.nospam.com> wrote in message news:eySKSR%23eFHA.2244@.TK2MSFTNGP15.phx.gbl...
> Hi Tibor,
> Actually - I really meant to ask the question about Differential backups
> (and not Incremental). I just had my terminology messed up.
> So - would I be able to do this for Differential backups...
> 1. Perform a full DB backup
> 2. Set the recovery model to Simple
> 3. Run the upgrade
> 4. Set the recovery model back to Full
> 5. Run a differential backup
> Thanks!
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
> message news:u4zfMN%23eFHA.3012@.tk2msftngp13.phx.gbl...
> server) are based on the
> you wouldn't be able to
> news:OWT5nJ%23eFHA.3808@.TK2MSFTNGP14.phx.gbl...
> transaction
> order
> to be
> the
>
|||I can backup 90GB in just a few minutes using no third party tools
How long is "Too Long" ?
What kind of IO subSystem do you have ? (RAID Array, SAN, NAS)
Greg Jackson
PDX, Oregon

Can Incremental Backup be done with Simple recovery Model?

For SQL2000 - Just wondering if the incremental backup requires transaction
logs.
We have a database upgrade process that performs a lot of updates. In order
to keep the transaction log from growing out of control - I would like to be
able to set the recovery model as "simple". I am hoping that I could do the
following:
1. Perform a full DB backup
2. Set the recovery model to Simple
3. Run the upgrade
4. Set the recovery model back to Full
5. Run an incremental backup
Does this sound reasonable? Should steps 4 and 5 be reversed?
Thanks in advance.No, Incremental backups (which are called transaction log backups in SQL ser
ver) are based on the
transaction log. If you are missing log records in the transaction log, you
wouldn't be able to
restore from the transaction log backups.
Consider differential backups, perhaps?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"TJT" <TJT@.nospam.com> wrote in message news:OWT5nJ%23eFHA.3808@.TK2MSFTNGP14.phx.gbl...[vbco
l=seagreen]
> For SQL2000 - Just wondering if the incremental backup requires transactio
n
> logs.
> We have a database upgrade process that performs a lot of updates. In ord
er
> to keep the transaction log from growing out of control - I would like to
be
> able to set the recovery model as "simple". I am hoping that I could do t
he
> following:
> 1. Perform a full DB backup
> 2. Set the recovery model to Simple
> 3. Run the upgrade
> 4. Set the recovery model back to Full
> 5. Run an incremental backup
> Does this sound reasonable? Should steps 4 and 5 be reversed?
> Thanks in advance.
>[/vbcol]|||"TJT" <TJT@.nospam.com> wrote in message
news:OWT5nJ#eFHA.3808@.TK2MSFTNGP14.phx.gbl...
> For SQL2000 - Just wondering if the incremental backup requires
transaction
> logs.
> We have a database upgrade process that performs a lot of updates. In
order
> to keep the transaction log from growing out of control - I would like to
be
> able to set the recovery model as "simple". I am hoping that I could do
the
> following:
> 1. Perform a full DB backup
> 2. Set the recovery model to Simple
> 3. Run the upgrade
> 4. Set the recovery model back to Full
> 5. Run an incremental backup
> Does this sound reasonable? Should steps 4 and 5 be reversed?
> Thanks in advance.
>
If this is a one-time upgrade, I would suggest the following...
1. Perform Full DB Backup
2. Set to Simple
3. Run upgrade
4. Perform Full DB Backup
5. Test your upgraded information. If all is OK
6. Set recovery back to full.
I'm not sure why you need the incrementals.
Rick Sawtell
MCT, MCSD, MCDBA|||Hi Tibor,
Actually - I really meant to ask the question about Differential backups
(and not Incremental). I just had my terminology messed up.
So - would I be able to do this for Differential backups...
1. Perform a full DB backup
2. Set the recovery model to Simple
3. Run the upgrade
4. Set the recovery model back to Full
5. Run a differential backup
Thanks!
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:u4zfMN%23eFHA.3012@.tk2msftngp13.phx.gbl...
> No, Incremental backups (which are called transaction log backups in SQL
server) are based on the
> transaction log. If you are missing log records in the transaction log,
you wouldn't be able to
> restore from the transaction log backups.
> Consider differential backups, perhaps?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "TJT" <TJT@.nospam.com> wrote in message
news:OWT5nJ%23eFHA.3808@.TK2MSFTNGP14.phx.gbl...
transaction[vbcol=seagreen]
order[vbcol=seagreen]
to be[vbcol=seagreen]
the[vbcol=seagreen]
>|||Hi Rick,
The database is rather large (90GB) and we are trying to minimize downtime.
This is why I was hoping to perform a differential backup.
If the database were small and downtime were not a problem - I would perform
another Full backup after the upgrade as you suggest.
Thanks,
Tom
"Rick Sawtell" <r_sawtell@.hotmail.com> wrote in message
news:uvuhVO%23eFHA.1448@.TK2MSFTNGP14.phx.gbl...
> "TJT" <TJT@.nospam.com> wrote in message
> news:OWT5nJ#eFHA.3808@.TK2MSFTNGP14.phx.gbl...
> transaction
> order
to[vbcol=seagreen]
> be
> the
> If this is a one-time upgrade, I would suggest the following...
> 1. Perform Full DB Backup
> 2. Set to Simple
> 3. Run upgrade
> 4. Perform Full DB Backup
> 5. Test your upgraded information. If all is OK
> 6. Set recovery back to full.
>
> I'm not sure why you need the incrementals.
> Rick Sawtell
> MCT, MCSD, MCDBA
>
>|||Yes, that should work. Just test on a test server that the steps are fine fi
rst (possibly with less
data volume). Also, be aware that you have now broken your chains of log bac
kups. The log backup
taken after this will not be able to apply after a log backup taken before a
ll this. Only from the
last db backup.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"TJT" <TJT@.nospam.com> wrote in message news:eySKSR%23eFHA.2244@.TK2MSFTNGP15.phx.gbl...[vbco
l=seagreen]
> Hi Tibor,
> Actually - I really meant to ask the question about Differential backups
> (and not Incremental). I just had my terminology messed up.
> So - would I be able to do this for Differential backups...
> 1. Perform a full DB backup
> 2. Set the recovery model to Simple
> 3. Run the upgrade
> 4. Set the recovery model back to Full
> 5. Run a differential backup
> Thanks!
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote i
n
> message news:u4zfMN%23eFHA.3012@.tk2msftngp13.phx.gbl...
> server) are based on the
> you wouldn't be able to
> news:OWT5nJ%23eFHA.3808@.TK2MSFTNGP14.phx.gbl...
> transaction
> order
> to be
> the
>[/vbcol]|||I can backup 90GB in just a few minutes using no third party tools
How long is "Too Long" ?
What kind of IO subSystem do you have ? (RAID Array, SAN, NAS)
Greg Jackson
PDX, Oregon

Can Incremental Backup be done with Simple recovery Model?

For SQL2000 - Just wondering if the incremental backup requires transaction
logs.
We have a database upgrade process that performs a lot of updates. In order
to keep the transaction log from growing out of control - I would like to be
able to set the recovery model as "simple". I am hoping that I could do the
following:
1. Perform a full DB backup
2. Set the recovery model to Simple
3. Run the upgrade
4. Set the recovery model back to Full
5. Run an incremental backup
Does this sound reasonable? Should steps 4 and 5 be reversed?
Thanks in advance.No, Incremental backups (which are called transaction log backups in SQL server) are based on the
transaction log. If you are missing log records in the transaction log, you wouldn't be able to
restore from the transaction log backups.
Consider differential backups, perhaps?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"TJT" <TJT@.nospam.com> wrote in message news:OWT5nJ%23eFHA.3808@.TK2MSFTNGP14.phx.gbl...
> For SQL2000 - Just wondering if the incremental backup requires transaction
> logs.
> We have a database upgrade process that performs a lot of updates. In order
> to keep the transaction log from growing out of control - I would like to be
> able to set the recovery model as "simple". I am hoping that I could do the
> following:
> 1. Perform a full DB backup
> 2. Set the recovery model to Simple
> 3. Run the upgrade
> 4. Set the recovery model back to Full
> 5. Run an incremental backup
> Does this sound reasonable? Should steps 4 and 5 be reversed?
> Thanks in advance.
>|||"TJT" <TJT@.nospam.com> wrote in message
news:OWT5nJ#eFHA.3808@.TK2MSFTNGP14.phx.gbl...
> For SQL2000 - Just wondering if the incremental backup requires
transaction
> logs.
> We have a database upgrade process that performs a lot of updates. In
order
> to keep the transaction log from growing out of control - I would like to
be
> able to set the recovery model as "simple". I am hoping that I could do
the
> following:
> 1. Perform a full DB backup
> 2. Set the recovery model to Simple
> 3. Run the upgrade
> 4. Set the recovery model back to Full
> 5. Run an incremental backup
> Does this sound reasonable? Should steps 4 and 5 be reversed?
> Thanks in advance.
>
If this is a one-time upgrade, I would suggest the following...
1. Perform Full DB Backup
2. Set to Simple
3. Run upgrade
4. Perform Full DB Backup
5. Test your upgraded information. If all is OK
6. Set recovery back to full.
I'm not sure why you need the incrementals.
Rick Sawtell
MCT, MCSD, MCDBA|||Hi Tibor,
Actually - I really meant to ask the question about Differential backups
(and not Incremental). I just had my terminology messed up.
So - would I be able to do this for Differential backups...
1. Perform a full DB backup
2. Set the recovery model to Simple
3. Run the upgrade
4. Set the recovery model back to Full
5. Run a differential backup
Thanks!
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:u4zfMN%23eFHA.3012@.tk2msftngp13.phx.gbl...
> No, Incremental backups (which are called transaction log backups in SQL
server) are based on the
> transaction log. If you are missing log records in the transaction log,
you wouldn't be able to
> restore from the transaction log backups.
> Consider differential backups, perhaps?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "TJT" <TJT@.nospam.com> wrote in message
news:OWT5nJ%23eFHA.3808@.TK2MSFTNGP14.phx.gbl...
> > For SQL2000 - Just wondering if the incremental backup requires
transaction
> > logs.
> >
> > We have a database upgrade process that performs a lot of updates. In
order
> > to keep the transaction log from growing out of control - I would like
to be
> > able to set the recovery model as "simple". I am hoping that I could do
the
> > following:
> > 1. Perform a full DB backup
> > 2. Set the recovery model to Simple
> > 3. Run the upgrade
> > 4. Set the recovery model back to Full
> > 5. Run an incremental backup
> >
> > Does this sound reasonable? Should steps 4 and 5 be reversed?
> >
> > Thanks in advance.
> >
> >
>|||Hi Rick,
The database is rather large (90GB) and we are trying to minimize downtime.
This is why I was hoping to perform a differential backup.
If the database were small and downtime were not a problem - I would perform
another Full backup after the upgrade as you suggest.
Thanks,
Tom
"Rick Sawtell" <r_sawtell@.hotmail.com> wrote in message
news:uvuhVO%23eFHA.1448@.TK2MSFTNGP14.phx.gbl...
> "TJT" <TJT@.nospam.com> wrote in message
> news:OWT5nJ#eFHA.3808@.TK2MSFTNGP14.phx.gbl...
> > For SQL2000 - Just wondering if the incremental backup requires
> transaction
> > logs.
> >
> > We have a database upgrade process that performs a lot of updates. In
> order
> > to keep the transaction log from growing out of control - I would like
to
> be
> > able to set the recovery model as "simple". I am hoping that I could do
> the
> > following:
> > 1. Perform a full DB backup
> > 2. Set the recovery model to Simple
> > 3. Run the upgrade
> > 4. Set the recovery model back to Full
> > 5. Run an incremental backup
> >
> > Does this sound reasonable? Should steps 4 and 5 be reversed?
> >
> > Thanks in advance.
> >
> >
> If this is a one-time upgrade, I would suggest the following...
> 1. Perform Full DB Backup
> 2. Set to Simple
> 3. Run upgrade
> 4. Perform Full DB Backup
> 5. Test your upgraded information. If all is OK
> 6. Set recovery back to full.
>
> I'm not sure why you need the incrementals.
> Rick Sawtell
> MCT, MCSD, MCDBA
>
>|||Yes, that should work. Just test on a test server that the steps are fine first (possibly with less
data volume). Also, be aware that you have now broken your chains of log backups. The log backup
taken after this will not be able to apply after a log backup taken before all this. Only from the
last db backup.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"TJT" <TJT@.nospam.com> wrote in message news:eySKSR%23eFHA.2244@.TK2MSFTNGP15.phx.gbl...
> Hi Tibor,
> Actually - I really meant to ask the question about Differential backups
> (and not Incremental). I just had my terminology messed up.
> So - would I be able to do this for Differential backups...
> 1. Perform a full DB backup
> 2. Set the recovery model to Simple
> 3. Run the upgrade
> 4. Set the recovery model back to Full
> 5. Run a differential backup
> Thanks!
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
> message news:u4zfMN%23eFHA.3012@.tk2msftngp13.phx.gbl...
>> No, Incremental backups (which are called transaction log backups in SQL
> server) are based on the
>> transaction log. If you are missing log records in the transaction log,
> you wouldn't be able to
>> restore from the transaction log backups.
>> Consider differential backups, perhaps?
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "TJT" <TJT@.nospam.com> wrote in message
> news:OWT5nJ%23eFHA.3808@.TK2MSFTNGP14.phx.gbl...
>> > For SQL2000 - Just wondering if the incremental backup requires
> transaction
>> > logs.
>> >
>> > We have a database upgrade process that performs a lot of updates. In
> order
>> > to keep the transaction log from growing out of control - I would like
> to be
>> > able to set the recovery model as "simple". I am hoping that I could do
> the
>> > following:
>> > 1. Perform a full DB backup
>> > 2. Set the recovery model to Simple
>> > 3. Run the upgrade
>> > 4. Set the recovery model back to Full
>> > 5. Run an incremental backup
>> >
>> > Does this sound reasonable? Should steps 4 and 5 be reversed?
>> >
>> > Thanks in advance.
>> >
>> >
>>
>|||I can backup 90GB in just a few minutes using no third party tools
How long is "Too Long" ?
What kind of IO subSystem do you have ? (RAID Array, SAN, NAS)
Greg Jackson
PDX, Oregon

Thursday, March 8, 2012

Can I use SSRS2005 with SQL Server 2000

Hi, stupid question...haven't tried it myself, so I'll ask...
I have a client who is using SQL Server 2000, and can't upgrade to 2005
anytime soon. However, I'd like to use SSRS 2005 instead of SSRS 2000
to build some reports.
Can this be done? Are there any major issues?
Thanks,
KevinRS 2005 will use SQL 2000 as its object cache/metadata store. However, you
need to have a SQL 2005 license to use RS 2005 in this configuration.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Kevin" <kgoff@.att.net> wrote in message
news:Oyw55sA7HHA.1148@.TK2MSFTNGP05.phx.gbl...
> Hi, stupid question...haven't tried it myself, so I'll ask...
> I have a client who is using SQL Server 2000, and can't upgrade to 2005
> anytime soon. However, I'd like to use SSRS 2005 instead of SSRS 2000 to
> build some reports.
> Can this be done? Are there any major issues?
> Thanks,
> Kevin
>

Wednesday, March 7, 2012

Can I use RDO with MDAC 2.8?

Hi,
I have some apps that use RDO and I would like to upgrade MDAC from
2.5 to 2.8. Will the apps continue to work or will I have to make
changes to them?
Thanks,
Marty
Hi
I think this will be fine, but you may want to test thoroughly on one system
first.
John
"Marty" <marty@.australiamail.com> wrote in message
news:29d7efad.0406142058.5d6212b6@.posting.google.c om...
> Hi,
> I have some apps that use RDO and I would like to upgrade MDAC from
> 2.5 to 2.8. Will the apps continue to work or will I have to make
> changes to them?
> Thanks,
> Marty

Can I use RDO with MDAC 2.8?

Hi,
I have some apps that use RDO and I would like to upgrade MDAC from
2.5 to 2.8. Will the apps continue to work or will I have to make
changes to them?
Thanks,
MartyHi
I think this will be fine, but you may want to test thoroughly on one system
first.
John
"Marty" <marty@.australiamail.com> wrote in message
news:29d7efad.0406142058.5d6212b6@.posting.google.com...
> Hi,
> I have some apps that use RDO and I would like to upgrade MDAC from
> 2.5 to 2.8. Will the apps continue to work or will I have to make
> changes to them?
> Thanks,
> Marty

Can I use RDO with MDAC 2.8?

Hi,
I have some apps that use RDO and I would like to upgrade MDAC from
2.5 to 2.8. Will the apps continue to work or will I have to make
changes to them?
Thanks,
MartyHi
I think this will be fine, but you may want to test thoroughly on one system
first.
John
"Marty" <marty@.australiamail.com> wrote in message
news:29d7efad.0406142058.5d6212b6@.posting.google.com...
> Hi,
> I have some apps that use RDO and I would like to upgrade MDAC from
> 2.5 to 2.8. Will the apps continue to work or will I have to make
> changes to them?
> Thanks,
> Marty

Saturday, February 25, 2012

Can I use data drive subscription on a remote sql standard version

I would like to upgrade our report server to sql 2000 enterprise
edition to be able to use the DD subscriptions.. if I do do upgrade the
server, will I be able to connect to a sql server on another box with
the standard version and continue to use DD subscriptions on that
remote server.
or is there another way to get around this issue by way of stored
procedures.. thanks.What specifically do you mean by "continue to use DD susbscriptions no that
remote server"? Do you mean the remote server is the source of data that
drives the DD subscription? In that case, yes.
-Tim
"Joaquin" <joaquin.pineda@.gmail.com> wrote in message
news:1147897141.934976.263120@.38g2000cwa.googlegroups.com...
>I would like to upgrade our report server to sql 2000 enterprise
> edition to be able to use the DD subscriptions.. if I do do upgrade the
> server, will I be able to connect to a sql server on another box with
> the standard version and continue to use DD subscriptions on that
> remote server.
> or is there another way to get around this issue by way of stored
> procedures.. thanks.
>|||Tim Dot NoSpam wrote:
> What specifically do you mean by "continue to use DD susbscriptions no that
> remote server"? Do you mean the remote server is the source of data that
> drives the DD subscription? In that case, yes.
>
Tim, you got it, that's what I wanted to know. also, do you know if its
possible to simulate dd subscriptions, let say by way of stored proc?
on standard version of sql. thanks.

Friday, February 24, 2012

can i upgrade from sql 2005 express to sql server 2005 enterprise edition ?

if i upgrade from sql server 2005 expressto sql server 2005 enterprise can i do it ?
am i need to uninstall 2005 express before ?

hi,

as per ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/instsql9/html/702359c4-6ca9-42a8-860c-a95a802898a1.htm help topic of Books OnLine, you can upgrade to all 32bit editions of SQL Server 2005, including

SQL Server 2005 Enterprise Edition

SQL Server 2005 Developer Edition

SQL Server 2005 Standard Edition

SQL Server 2005 Workgroup Edition

SQL Server 2005 Express Edition with Advanced Services

a similar matrix is available on www.microsoft.com/sql sub area too, but at the moment it seems I'm unable to access Microsoft web site..

regards

Sunday, February 19, 2012

Can I somehow subscribe to SQL upgrade notifications?

Well, it's happened again. An upgrade to SQL server was released without my having any idea about it. SP2 came out today and the only way I knew it was I happened to see a headline on Yahoo. Similar things have happened in the past with HotFixes or security rollups. Sometimes it's rather embarrassing, especially when your boss challenges you on the most recent security updates for SQL. Is there any way which we can be notified of new upgrades/updates to SQL Server? I need to know when there is a new hotfix, update, service pack, or whatever so that I can install it as needed. So far, the only way I've found these was by accident. I'm signed up with the Microsoft Download Notification email list, so I was able to see that SP2 CTPs were released, but I've never seen it include hotfixes or rollups.

If something like a SQL update notification service doesn't exist, then I would ask that Microsoft look at putting one together. Thank you!

The download notifications only send out once a week according to the site. http://www.microsoft.com/downloads/render.aspx?content=notifications&displaylang=en

Another good way would be to check out the SQL Server Release Services blog (http://blogs.msdn.com/sqlreleaseservices/) or the other SQL sites linked from Microsoft.com http://www.microsoft.com/sql, http://www.microsoft.com/technet/prodtechnol/sql, and http://msdn.microsoft.com/sql.

Thanks,
Sam Lester (MSFT)

Friday, February 10, 2012

can i keep sql server 2000 if upgrade win 2000 to win 2003 (was "sql server 2000

Hello, i have a question that the sql server 2000 is install in window 2000 server. If i want to update to window 2003. Is that any problem in sql server 2000. I am worry about whether we will have problem after update. What i need to do? Many thanks.Updating operating systems is a bit dodgy. You might want to back everything up, do a fresh install, and restore all the backups.

If you have to do the update, then SQL Server 2000 >SHOULD< run, so long as you have SQL SP3 installed.

Keep in mind, though, you should check with Microsoft before you do this to your really-important-finance database server. Opinions are not guarantees.|||Opinions are not guarantees.
--But, I would lay money down on this one. [:)] If this server is important, I wouldn't even consider upgrading the OS. Backup the files, format the drive, install 2003, install SQL Server, restore the databases.

It takes more time. It's safer. If this is a production server, that's the route I would take.|||i taught that when u upgrade it wipes out the application and writes a new operating system

better back up|||taught or thought??
......nevermind|||does it matter ! think like a good thought !! haa