Hi,
I read the licensing page, but still i'm confused ... as always with
licensing stuff.
I have a VB 6.0 application (.exe) that establish the connection to my
Access database, but we might want to switch to SQL Server2000 in a near
future.
Our situation
Maximum # of users to use my VB application will be 20. That means I will
deploy my VB app on 20 computers. BUT my VB application will always logon to
the database using the same user.
What would be the best licensing model for me considering all these facts?
1- Connection established from a VB application interface.
2- 20 computers will run the VB application
3- On the 20 computers running the VB app, the SQL user to establish the
connection will always be the same. So only 1 user.
Few more users won't use the VB app and will connect to the database from
the Entreprise Manager (2-3 users)
SQL Server...
Entreprise or Standard. I wonder if standard can do the job for us, it is a
lot cheaper. I think yes. What's the big difference between the two? We
don't need the super big thing here.
Thanks for helping.
Dominic.
SQL User = End user for licensing. A license User is not the same as a
connection or a login. Count the TOTAL number of users that access the
data. That is how many CALs you need. If the CAL cost exceeds a
per-processor license, purchase a per-processor license.
Your VB application is considered "middleware" or a "user aggregator" for
licensing purposes. As such you remove it from consideration entirely.
Enterprise vs. Standard Edition SQL choice should be based on which features
you need. IMHO a decent application with 20 or fewer users should work just
fine on Standard Edition.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"dbelley_office" <dbelley_office@.discussions.microsoft.com> wrote in message
news:F93D8030-77CD-4EDE-87D6-D05BCC44DBF3@.microsoft.com...
> Hi,
> I read the licensing page, but still i'm confused ... as always with
> licensing stuff.
> I have a VB 6.0 application (.exe) that establish the connection to my
> Access database, but we might want to switch to SQL Server2000 in a near
> future.
> Our situation
> --
> Maximum # of users to use my VB application will be 20. That means I will
> deploy my VB app on 20 computers. BUT my VB application will always logon
to
> the database using the same user.
> What would be the best licensing model for me considering all these facts?
> 1- Connection established from a VB application interface.
> 2- 20 computers will run the VB application
> 3- On the 20 computers running the VB app, the SQL user to establish the
> connection will always be the same. So only 1 user.
> Few more users won't use the VB app and will connect to the database from
> the Entreprise Manager (2-3 users)
> SQL Server...
> Entreprise or Standard. I wonder if standard can do the job for us, it is
a
> lot cheaper. I think yes. What's the big difference between the two? We
> don't need the super big thing here.
>
> Thanks for helping.
> Dominic.
|||Ok.
So if I have 1 computer accessing the data. But 3 users can be working on
that computer.
The cheaper and legal licensing model for me would be to go with the Server
Plus Device CAL, right? And would only buy 1 license.
-- ON THE OTHER HAND --
If I have 3 computers accessing the data, but only 1 user can be working on
that computer.
Than I would go with the Server Plus User CAL, right? And again would only
buy 1 license.
For Server Licensing.
I'm not familiar with SQL Server and won't be my task to administrate it.
But if I want 2 or more instances of database ( Production, QA, Development
). Is this all reside on the same server installation so only 1 server
license is enough.
Or I can only install 1 database on a machine(production) and other(qa &
dev) would need to be on other machine? So I would need 3 server licenses?
I guess I can have multiple instances on only 1 computer, but I only want to
make sure. This technical stuff is not my field of expertise.
Thanks.
"Geoff N. Hiten" wrote:
> SQL User = End user for licensing. A license User is not the same as a
> connection or a login. Count the TOTAL number of users that access the
> data. That is how many CALs you need. If the CAL cost exceeds a
> per-processor license, purchase a per-processor license.
> Your VB application is considered "middleware" or a "user aggregator" for
> licensing purposes. As such you remove it from consideration entirely.
> Enterprise vs. Standard Edition SQL choice should be based on which features
> you need. IMHO a decent application with 20 or fewer users should work just
> fine on Standard Edition.
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "dbelley_office" <dbelley_office@.discussions.microsoft.com> wrote in message
> news:F93D8030-77CD-4EDE-87D6-D05BCC44DBF3@.microsoft.com...
> to
> a
>
>
|||I would call your local Microsoft office and ask to speak to a sales and
licensing person. They are the only ones that have the 'Legal and Official"
answers.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"dbelley_office" <dbelley_office@.discussions.microsoft.com> wrote in message
news:B453E6CD-E0F7-4205-BB39-53D1D16D5778@.microsoft.com...
> Ok.
> So if I have 1 computer accessing the data. But 3 users can be working on
> that computer.
> The cheaper and legal licensing model for me would be to go with the
Server
> Plus Device CAL, right? And would only buy 1 license.
> -- ON THE OTHER HAND --
> If I have 3 computers accessing the data, but only 1 user can be working
on
> that computer.
> Than I would go with the Server Plus User CAL, right? And again would
only
> buy 1 license.
>
> For Server Licensing.
> I'm not familiar with SQL Server and won't be my task to administrate it.
> But if I want 2 or more instances of database ( Production, QA,
Development
> ). Is this all reside on the same server installation so only 1 server
> license is enough.
> Or I can only install 1 database on a machine(production) and other(qa &
> dev) would need to be on other machine? So I would need 3 server
licenses?
> I guess I can have multiple instances on only 1 computer, but I only want
to[vbcol=seagreen]
> make sure. This technical stuff is not my field of expertise.
> Thanks.
>
> "Geoff N. Hiten" wrote:
for[vbcol=seagreen]
features[vbcol=seagreen]
just[vbcol=seagreen]
message[vbcol=seagreen]
near[vbcol=seagreen]
will[vbcol=seagreen]
logon[vbcol=seagreen]
facts?[vbcol=seagreen]
the[vbcol=seagreen]
from[vbcol=seagreen]
it is[vbcol=seagreen]
We[vbcol=seagreen]
Showing posts with label product. Show all posts
Showing posts with label product. Show all posts
Wednesday, March 28, 2012
Help for licensing and proper product for us.
Hi,
I read the licensing page, but still i'm confused ... as always with
licensing stuff.
I have a VB 6.0 application (.exe) that establish the connection to my
Access database, but we might want to switch to SQL Server2000 in a near
future.
Our situation
--
Maximum # of users to use my VB application will be 20. That means I will
deploy my VB app on 20 computers. BUT my VB application will always logon t
o
the database using the same user.
What would be the best licensing model for me considering all these facts?
1- Connection established from a VB application interface.
2- 20 computers will run the VB application
3- On the 20 computers running the VB app, the SQL user to establish the
connection will always be the same. So only 1 user.
Few more users won't use the VB app and will connect to the database from
the Entreprise Manager (2-3 users)
SQL Server...
Entreprise or Standard. I wonder if standard can do the job for us, it is a
lot cheaper. I think yes. What's the big difference between the two? We
don't need the super big thing here.
Thanks for helping.
Dominic.SQL User = End user for licensing. A license User is not the same as a
connection or a login. Count the TOTAL number of users that access the
data. That is how many CALs you need. If the CAL cost exceeds a
per-processor license, purchase a per-processor license.
Your VB application is considered "middleware" or a "user aggregator" for
licensing purposes. As such you remove it from consideration entirely.
Enterprise vs. Standard Edition SQL choice should be based on which features
you need. IMHO a decent application with 20 or fewer users should work just
fine on Standard Edition.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"dbelley_office" <dbelley_office@.discussions.microsoft.com> wrote in message
news:F93D8030-77CD-4EDE-87D6-D05BCC44DBF3@.microsoft.com...
> Hi,
> I read the licensing page, but still i'm confused ... as always with
> licensing stuff.
> I have a VB 6.0 application (.exe) that establish the connection to my
> Access database, but we might want to switch to SQL Server2000 in a near
> future.
> Our situation
> --
> Maximum # of users to use my VB application will be 20. That means I will
> deploy my VB app on 20 computers. BUT my VB application will always logon
to
> the database using the same user.
> What would be the best licensing model for me considering all these facts?
> 1- Connection established from a VB application interface.
> 2- 20 computers will run the VB application
> 3- On the 20 computers running the VB app, the SQL user to establish the
> connection will always be the same. So only 1 user.
> Few more users won't use the VB app and will connect to the database from
> the Entreprise Manager (2-3 users)
> SQL Server...
> Entreprise or Standard. I wonder if standard can do the job for us, it is
a
> lot cheaper. I think yes. What's the big difference between the two? We
> don't need the super big thing here.
>
> Thanks for helping.
> Dominic.|||Ok.
So if I have 1 computer accessing the data. But 3 users can be working on
that computer.
The cheaper and legal licensing model for me would be to go with the Server
Plus Device CAL, right? And would only buy 1 license.
-- ON THE OTHER HAND --
If I have 3 computers accessing the data, but only 1 user can be working on
that computer.
Than I would go with the Server Plus User CAL, right? And again would only
buy 1 license.
---
For Server Licensing.
I'm not familiar with SQL Server and won't be my task to administrate it.
But if I want 2 or more instances of database ( Production, QA, Development
). Is this all reside on the same server installation so only 1 server
license is enough.
Or I can only install 1 database on a machine(production) and other(qa &
dev) would need to be on other machine? So I would need 3 server licenses?
I guess I can have multiple instances on only 1 computer, but I only want to
make sure. This technical stuff is not my field of expertise.
Thanks.
"Geoff N. Hiten" wrote:
> SQL User = End user for licensing. A license User is not the same as a
> connection or a login. Count the TOTAL number of users that access the
> data. That is how many CALs you need. If the CAL cost exceeds a
> per-processor license, purchase a per-processor license.
> Your VB application is considered "middleware" or a "user aggregator" for
> licensing purposes. As such you remove it from consideration entirely.
> Enterprise vs. Standard Edition SQL choice should be based on which featur
es
> you need. IMHO a decent application with 20 or fewer users should work ju
st
> fine on Standard Edition.
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "dbelley_office" <dbelley_office@.discussions.microsoft.com> wrote in messa
ge
> news:F93D8030-77CD-4EDE-87D6-D05BCC44DBF3@.microsoft.com...
> to
> a
>
>|||I would call your local Microsoft office and ask to speak to a sales and
licensing person. They are the only ones that have the 'Legal and Official"
answers.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"dbelley_office" <dbelley_office@.discussions.microsoft.com> wrote in message
news:B453E6CD-E0F7-4205-BB39-53D1D16D5778@.microsoft.com...
> Ok.
> So if I have 1 computer accessing the data. But 3 users can be working on
> that computer.
> The cheaper and legal licensing model for me would be to go with the
Server
> Plus Device CAL, right? And would only buy 1 license.
> -- ON THE OTHER HAND --
> If I have 3 computers accessing the data, but only 1 user can be working
on
> that computer.
> Than I would go with the Server Plus User CAL, right? And again would
only
> buy 1 license.
> ---
> For Server Licensing.
> I'm not familiar with SQL Server and won't be my task to administrate it.
> But if I want 2 or more instances of database ( Production, QA,
Development
> ). Is this all reside on the same server installation so only 1 server
> license is enough.
> Or I can only install 1 database on a machine(production) and other(qa &
> dev) would need to be on other machine? So I would need 3 server
licenses?
> I guess I can have multiple instances on only 1 computer, but I only want
to[vbcol=seagreen]
> make sure. This technical stuff is not my field of expertise.
> Thanks.
>
> "Geoff N. Hiten" wrote:
>
for[vbcol=seagreen]
features[vbcol=seagreen]
just[vbcol=seagreen]
message[vbcol=seagreen]
near[vbcol=seagreen]
will[vbcol=seagreen]
logon[vbcol=seagreen]
facts?[vbcol=seagreen]
the[vbcol=seagreen]
from[vbcol=seagreen]
it is[vbcol=seagreen]
We[vbcol=seagreen]
I read the licensing page, but still i'm confused ... as always with
licensing stuff.
I have a VB 6.0 application (.exe) that establish the connection to my
Access database, but we might want to switch to SQL Server2000 in a near
future.
Our situation
--
Maximum # of users to use my VB application will be 20. That means I will
deploy my VB app on 20 computers. BUT my VB application will always logon t
o
the database using the same user.
What would be the best licensing model for me considering all these facts?
1- Connection established from a VB application interface.
2- 20 computers will run the VB application
3- On the 20 computers running the VB app, the SQL user to establish the
connection will always be the same. So only 1 user.
Few more users won't use the VB app and will connect to the database from
the Entreprise Manager (2-3 users)
SQL Server...
Entreprise or Standard. I wonder if standard can do the job for us, it is a
lot cheaper. I think yes. What's the big difference between the two? We
don't need the super big thing here.
Thanks for helping.
Dominic.SQL User = End user for licensing. A license User is not the same as a
connection or a login. Count the TOTAL number of users that access the
data. That is how many CALs you need. If the CAL cost exceeds a
per-processor license, purchase a per-processor license.
Your VB application is considered "middleware" or a "user aggregator" for
licensing purposes. As such you remove it from consideration entirely.
Enterprise vs. Standard Edition SQL choice should be based on which features
you need. IMHO a decent application with 20 or fewer users should work just
fine on Standard Edition.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"dbelley_office" <dbelley_office@.discussions.microsoft.com> wrote in message
news:F93D8030-77CD-4EDE-87D6-D05BCC44DBF3@.microsoft.com...
> Hi,
> I read the licensing page, but still i'm confused ... as always with
> licensing stuff.
> I have a VB 6.0 application (.exe) that establish the connection to my
> Access database, but we might want to switch to SQL Server2000 in a near
> future.
> Our situation
> --
> Maximum # of users to use my VB application will be 20. That means I will
> deploy my VB app on 20 computers. BUT my VB application will always logon
to
> the database using the same user.
> What would be the best licensing model for me considering all these facts?
> 1- Connection established from a VB application interface.
> 2- 20 computers will run the VB application
> 3- On the 20 computers running the VB app, the SQL user to establish the
> connection will always be the same. So only 1 user.
> Few more users won't use the VB app and will connect to the database from
> the Entreprise Manager (2-3 users)
> SQL Server...
> Entreprise or Standard. I wonder if standard can do the job for us, it is
a
> lot cheaper. I think yes. What's the big difference between the two? We
> don't need the super big thing here.
>
> Thanks for helping.
> Dominic.|||Ok.
So if I have 1 computer accessing the data. But 3 users can be working on
that computer.
The cheaper and legal licensing model for me would be to go with the Server
Plus Device CAL, right? And would only buy 1 license.
-- ON THE OTHER HAND --
If I have 3 computers accessing the data, but only 1 user can be working on
that computer.
Than I would go with the Server Plus User CAL, right? And again would only
buy 1 license.
---
For Server Licensing.
I'm not familiar with SQL Server and won't be my task to administrate it.
But if I want 2 or more instances of database ( Production, QA, Development
). Is this all reside on the same server installation so only 1 server
license is enough.
Or I can only install 1 database on a machine(production) and other(qa &
dev) would need to be on other machine? So I would need 3 server licenses?
I guess I can have multiple instances on only 1 computer, but I only want to
make sure. This technical stuff is not my field of expertise.
Thanks.
"Geoff N. Hiten" wrote:
> SQL User = End user for licensing. A license User is not the same as a
> connection or a login. Count the TOTAL number of users that access the
> data. That is how many CALs you need. If the CAL cost exceeds a
> per-processor license, purchase a per-processor license.
> Your VB application is considered "middleware" or a "user aggregator" for
> licensing purposes. As such you remove it from consideration entirely.
> Enterprise vs. Standard Edition SQL choice should be based on which featur
es
> you need. IMHO a decent application with 20 or fewer users should work ju
st
> fine on Standard Edition.
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "dbelley_office" <dbelley_office@.discussions.microsoft.com> wrote in messa
ge
> news:F93D8030-77CD-4EDE-87D6-D05BCC44DBF3@.microsoft.com...
> to
> a
>
>|||I would call your local Microsoft office and ask to speak to a sales and
licensing person. They are the only ones that have the 'Legal and Official"
answers.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"dbelley_office" <dbelley_office@.discussions.microsoft.com> wrote in message
news:B453E6CD-E0F7-4205-BB39-53D1D16D5778@.microsoft.com...
> Ok.
> So if I have 1 computer accessing the data. But 3 users can be working on
> that computer.
> The cheaper and legal licensing model for me would be to go with the
Server
> Plus Device CAL, right? And would only buy 1 license.
> -- ON THE OTHER HAND --
> If I have 3 computers accessing the data, but only 1 user can be working
on
> that computer.
> Than I would go with the Server Plus User CAL, right? And again would
only
> buy 1 license.
> ---
> For Server Licensing.
> I'm not familiar with SQL Server and won't be my task to administrate it.
> But if I want 2 or more instances of database ( Production, QA,
Development
> ). Is this all reside on the same server installation so only 1 server
> license is enough.
> Or I can only install 1 database on a machine(production) and other(qa &
> dev) would need to be on other machine? So I would need 3 server
licenses?
> I guess I can have multiple instances on only 1 computer, but I only want
to[vbcol=seagreen]
> make sure. This technical stuff is not my field of expertise.
> Thanks.
>
> "Geoff N. Hiten" wrote:
>
for[vbcol=seagreen]
features[vbcol=seagreen]
just[vbcol=seagreen]
message[vbcol=seagreen]
near[vbcol=seagreen]
will[vbcol=seagreen]
logon[vbcol=seagreen]
facts?[vbcol=seagreen]
the[vbcol=seagreen]
from[vbcol=seagreen]
it is[vbcol=seagreen]
We[vbcol=seagreen]
Help for licensing and proper product for us.
Hi,
I read the licensing page, but still i'm confused ... as always with
licensing stuff.
I have a VB 6.0 application (.exe) that establish the connection to my
Access database, but we might want to switch to SQL Server2000 in a near
future.
Our situation
--
Maximum # of users to use my VB application will be 20. That means I will
deploy my VB app on 20 computers. BUT my VB application will always logon to
the database using the same user.
What would be the best licensing model for me considering all these facts?
1- Connection established from a VB application interface.
2- 20 computers will run the VB application
3- On the 20 computers running the VB app, the SQL user to establish the
connection will always be the same. So only 1 user.
Few more users won't use the VB app and will connect to the database from
the Entreprise Manager (2-3 users)
SQL Server...
Entreprise or Standard. I wonder if standard can do the job for us, it is a
lot cheaper. I think yes. What's the big difference between the two? We
don't need the super big thing here.
Thanks for helping.
Dominic.SQL User = End user for licensing. A license User is not the same as a
connection or a login. Count the TOTAL number of users that access the
data. That is how many CALs you need. If the CAL cost exceeds a
per-processor license, purchase a per-processor license.
Your VB application is considered "middleware" or a "user aggregator" for
licensing purposes. As such you remove it from consideration entirely.
Enterprise vs. Standard Edition SQL choice should be based on which features
you need. IMHO a decent application with 20 or fewer users should work just
fine on Standard Edition.
--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"dbelley_office" <dbelley_office@.discussions.microsoft.com> wrote in message
news:F93D8030-77CD-4EDE-87D6-D05BCC44DBF3@.microsoft.com...
> Hi,
> I read the licensing page, but still i'm confused ... as always with
> licensing stuff.
> I have a VB 6.0 application (.exe) that establish the connection to my
> Access database, but we might want to switch to SQL Server2000 in a near
> future.
> Our situation
> --
> Maximum # of users to use my VB application will be 20. That means I will
> deploy my VB app on 20 computers. BUT my VB application will always logon
to
> the database using the same user.
> What would be the best licensing model for me considering all these facts?
> 1- Connection established from a VB application interface.
> 2- 20 computers will run the VB application
> 3- On the 20 computers running the VB app, the SQL user to establish the
> connection will always be the same. So only 1 user.
> Few more users won't use the VB app and will connect to the database from
> the Entreprise Manager (2-3 users)
> SQL Server...
> Entreprise or Standard. I wonder if standard can do the job for us, it is
a
> lot cheaper. I think yes. What's the big difference between the two? We
> don't need the super big thing here.
>
> Thanks for helping.
> Dominic.|||Ok.
So if I have 1 computer accessing the data. But 3 users can be working on
that computer.
The cheaper and legal licensing model for me would be to go with the Server
Plus Device CAL, right? And would only buy 1 license.
-- ON THE OTHER HAND --
If I have 3 computers accessing the data, but only 1 user can be working on
that computer.
Than I would go with the Server Plus User CAL, right? And again would only
buy 1 license.
---
For Server Licensing.
I'm not familiar with SQL Server and won't be my task to administrate it.
But if I want 2 or more instances of database ( Production, QA, Development
). Is this all reside on the same server installation so only 1 server
license is enough.
Or I can only install 1 database on a machine(production) and other(qa &
dev) would need to be on other machine? So I would need 3 server licenses?
I guess I can have multiple instances on only 1 computer, but I only want to
make sure. This technical stuff is not my field of expertise.
Thanks.
"Geoff N. Hiten" wrote:
> SQL User = End user for licensing. A license User is not the same as a
> connection or a login. Count the TOTAL number of users that access the
> data. That is how many CALs you need. If the CAL cost exceeds a
> per-processor license, purchase a per-processor license.
> Your VB application is considered "middleware" or a "user aggregator" for
> licensing purposes. As such you remove it from consideration entirely.
> Enterprise vs. Standard Edition SQL choice should be based on which features
> you need. IMHO a decent application with 20 or fewer users should work just
> fine on Standard Edition.
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "dbelley_office" <dbelley_office@.discussions.microsoft.com> wrote in message
> news:F93D8030-77CD-4EDE-87D6-D05BCC44DBF3@.microsoft.com...
> > Hi,
> >
> > I read the licensing page, but still i'm confused ... as always with
> > licensing stuff.
> >
> > I have a VB 6.0 application (.exe) that establish the connection to my
> > Access database, but we might want to switch to SQL Server2000 in a near
> > future.
> >
> > Our situation
> > --
> > Maximum # of users to use my VB application will be 20. That means I will
> > deploy my VB app on 20 computers. BUT my VB application will always logon
> to
> > the database using the same user.
> >
> > What would be the best licensing model for me considering all these facts?
> > 1- Connection established from a VB application interface.
> > 2- 20 computers will run the VB application
> > 3- On the 20 computers running the VB app, the SQL user to establish the
> > connection will always be the same. So only 1 user.
> >
> > Few more users won't use the VB app and will connect to the database from
> > the Entreprise Manager (2-3 users)
> >
> > SQL Server...
> > Entreprise or Standard. I wonder if standard can do the job for us, it is
> a
> > lot cheaper. I think yes. What's the big difference between the two? We
> > don't need the super big thing here.
> >
> >
> > Thanks for helping.
> > Dominic.
>
>|||I would call your local Microsoft office and ask to speak to a sales and
licensing person. They are the only ones that have the 'Legal and Official"
answers.
--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"dbelley_office" <dbelley_office@.discussions.microsoft.com> wrote in message
news:B453E6CD-E0F7-4205-BB39-53D1D16D5778@.microsoft.com...
> Ok.
> So if I have 1 computer accessing the data. But 3 users can be working on
> that computer.
> The cheaper and legal licensing model for me would be to go with the
Server
> Plus Device CAL, right? And would only buy 1 license.
> -- ON THE OTHER HAND --
> If I have 3 computers accessing the data, but only 1 user can be working
on
> that computer.
> Than I would go with the Server Plus User CAL, right? And again would
only
> buy 1 license.
> ---
> For Server Licensing.
> I'm not familiar with SQL Server and won't be my task to administrate it.
> But if I want 2 or more instances of database ( Production, QA,
Development
> ). Is this all reside on the same server installation so only 1 server
> license is enough.
> Or I can only install 1 database on a machine(production) and other(qa &
> dev) would need to be on other machine? So I would need 3 server
licenses?
> I guess I can have multiple instances on only 1 computer, but I only want
to
> make sure. This technical stuff is not my field of expertise.
> Thanks.
>
> "Geoff N. Hiten" wrote:
> > SQL User = End user for licensing. A license User is not the same as a
> > connection or a login. Count the TOTAL number of users that access the
> > data. That is how many CALs you need. If the CAL cost exceeds a
> > per-processor license, purchase a per-processor license.
> >
> > Your VB application is considered "middleware" or a "user aggregator"
for
> > licensing purposes. As such you remove it from consideration entirely.
> >
> > Enterprise vs. Standard Edition SQL choice should be based on which
features
> > you need. IMHO a decent application with 20 or fewer users should work
just
> > fine on Standard Edition.
> >
> > --
> > Geoff N. Hiten
> > Microsoft SQL Server MVP
> > Senior Database Administrator
> > Careerbuilder.com
> >
> > I support the Professional Association for SQL Server
> > www.sqlpass.org
> >
> > "dbelley_office" <dbelley_office@.discussions.microsoft.com> wrote in
message
> > news:F93D8030-77CD-4EDE-87D6-D05BCC44DBF3@.microsoft.com...
> > > Hi,
> > >
> > > I read the licensing page, but still i'm confused ... as always with
> > > licensing stuff.
> > >
> > > I have a VB 6.0 application (.exe) that establish the connection to my
> > > Access database, but we might want to switch to SQL Server2000 in a
near
> > > future.
> > >
> > > Our situation
> > > --
> > > Maximum # of users to use my VB application will be 20. That means I
will
> > > deploy my VB app on 20 computers. BUT my VB application will always
logon
> > to
> > > the database using the same user.
> > >
> > > What would be the best licensing model for me considering all these
facts?
> > > 1- Connection established from a VB application interface.
> > > 2- 20 computers will run the VB application
> > > 3- On the 20 computers running the VB app, the SQL user to establish
the
> > > connection will always be the same. So only 1 user.
> > >
> > > Few more users won't use the VB app and will connect to the database
from
> > > the Entreprise Manager (2-3 users)
> > >
> > > SQL Server...
> > > Entreprise or Standard. I wonder if standard can do the job for us,
it is
> > a
> > > lot cheaper. I think yes. What's the big difference between the two?
We
> > > don't need the super big thing here.
> > >
> > >
> > > Thanks for helping.
> > > Dominic.
> >
> >
> >
I read the licensing page, but still i'm confused ... as always with
licensing stuff.
I have a VB 6.0 application (.exe) that establish the connection to my
Access database, but we might want to switch to SQL Server2000 in a near
future.
Our situation
--
Maximum # of users to use my VB application will be 20. That means I will
deploy my VB app on 20 computers. BUT my VB application will always logon to
the database using the same user.
What would be the best licensing model for me considering all these facts?
1- Connection established from a VB application interface.
2- 20 computers will run the VB application
3- On the 20 computers running the VB app, the SQL user to establish the
connection will always be the same. So only 1 user.
Few more users won't use the VB app and will connect to the database from
the Entreprise Manager (2-3 users)
SQL Server...
Entreprise or Standard. I wonder if standard can do the job for us, it is a
lot cheaper. I think yes. What's the big difference between the two? We
don't need the super big thing here.
Thanks for helping.
Dominic.SQL User = End user for licensing. A license User is not the same as a
connection or a login. Count the TOTAL number of users that access the
data. That is how many CALs you need. If the CAL cost exceeds a
per-processor license, purchase a per-processor license.
Your VB application is considered "middleware" or a "user aggregator" for
licensing purposes. As such you remove it from consideration entirely.
Enterprise vs. Standard Edition SQL choice should be based on which features
you need. IMHO a decent application with 20 or fewer users should work just
fine on Standard Edition.
--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"dbelley_office" <dbelley_office@.discussions.microsoft.com> wrote in message
news:F93D8030-77CD-4EDE-87D6-D05BCC44DBF3@.microsoft.com...
> Hi,
> I read the licensing page, but still i'm confused ... as always with
> licensing stuff.
> I have a VB 6.0 application (.exe) that establish the connection to my
> Access database, but we might want to switch to SQL Server2000 in a near
> future.
> Our situation
> --
> Maximum # of users to use my VB application will be 20. That means I will
> deploy my VB app on 20 computers. BUT my VB application will always logon
to
> the database using the same user.
> What would be the best licensing model for me considering all these facts?
> 1- Connection established from a VB application interface.
> 2- 20 computers will run the VB application
> 3- On the 20 computers running the VB app, the SQL user to establish the
> connection will always be the same. So only 1 user.
> Few more users won't use the VB app and will connect to the database from
> the Entreprise Manager (2-3 users)
> SQL Server...
> Entreprise or Standard. I wonder if standard can do the job for us, it is
a
> lot cheaper. I think yes. What's the big difference between the two? We
> don't need the super big thing here.
>
> Thanks for helping.
> Dominic.|||Ok.
So if I have 1 computer accessing the data. But 3 users can be working on
that computer.
The cheaper and legal licensing model for me would be to go with the Server
Plus Device CAL, right? And would only buy 1 license.
-- ON THE OTHER HAND --
If I have 3 computers accessing the data, but only 1 user can be working on
that computer.
Than I would go with the Server Plus User CAL, right? And again would only
buy 1 license.
---
For Server Licensing.
I'm not familiar with SQL Server and won't be my task to administrate it.
But if I want 2 or more instances of database ( Production, QA, Development
). Is this all reside on the same server installation so only 1 server
license is enough.
Or I can only install 1 database on a machine(production) and other(qa &
dev) would need to be on other machine? So I would need 3 server licenses?
I guess I can have multiple instances on only 1 computer, but I only want to
make sure. This technical stuff is not my field of expertise.
Thanks.
"Geoff N. Hiten" wrote:
> SQL User = End user for licensing. A license User is not the same as a
> connection or a login. Count the TOTAL number of users that access the
> data. That is how many CALs you need. If the CAL cost exceeds a
> per-processor license, purchase a per-processor license.
> Your VB application is considered "middleware" or a "user aggregator" for
> licensing purposes. As such you remove it from consideration entirely.
> Enterprise vs. Standard Edition SQL choice should be based on which features
> you need. IMHO a decent application with 20 or fewer users should work just
> fine on Standard Edition.
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "dbelley_office" <dbelley_office@.discussions.microsoft.com> wrote in message
> news:F93D8030-77CD-4EDE-87D6-D05BCC44DBF3@.microsoft.com...
> > Hi,
> >
> > I read the licensing page, but still i'm confused ... as always with
> > licensing stuff.
> >
> > I have a VB 6.0 application (.exe) that establish the connection to my
> > Access database, but we might want to switch to SQL Server2000 in a near
> > future.
> >
> > Our situation
> > --
> > Maximum # of users to use my VB application will be 20. That means I will
> > deploy my VB app on 20 computers. BUT my VB application will always logon
> to
> > the database using the same user.
> >
> > What would be the best licensing model for me considering all these facts?
> > 1- Connection established from a VB application interface.
> > 2- 20 computers will run the VB application
> > 3- On the 20 computers running the VB app, the SQL user to establish the
> > connection will always be the same. So only 1 user.
> >
> > Few more users won't use the VB app and will connect to the database from
> > the Entreprise Manager (2-3 users)
> >
> > SQL Server...
> > Entreprise or Standard. I wonder if standard can do the job for us, it is
> a
> > lot cheaper. I think yes. What's the big difference between the two? We
> > don't need the super big thing here.
> >
> >
> > Thanks for helping.
> > Dominic.
>
>|||I would call your local Microsoft office and ask to speak to a sales and
licensing person. They are the only ones that have the 'Legal and Official"
answers.
--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"dbelley_office" <dbelley_office@.discussions.microsoft.com> wrote in message
news:B453E6CD-E0F7-4205-BB39-53D1D16D5778@.microsoft.com...
> Ok.
> So if I have 1 computer accessing the data. But 3 users can be working on
> that computer.
> The cheaper and legal licensing model for me would be to go with the
Server
> Plus Device CAL, right? And would only buy 1 license.
> -- ON THE OTHER HAND --
> If I have 3 computers accessing the data, but only 1 user can be working
on
> that computer.
> Than I would go with the Server Plus User CAL, right? And again would
only
> buy 1 license.
> ---
> For Server Licensing.
> I'm not familiar with SQL Server and won't be my task to administrate it.
> But if I want 2 or more instances of database ( Production, QA,
Development
> ). Is this all reside on the same server installation so only 1 server
> license is enough.
> Or I can only install 1 database on a machine(production) and other(qa &
> dev) would need to be on other machine? So I would need 3 server
licenses?
> I guess I can have multiple instances on only 1 computer, but I only want
to
> make sure. This technical stuff is not my field of expertise.
> Thanks.
>
> "Geoff N. Hiten" wrote:
> > SQL User = End user for licensing. A license User is not the same as a
> > connection or a login. Count the TOTAL number of users that access the
> > data. That is how many CALs you need. If the CAL cost exceeds a
> > per-processor license, purchase a per-processor license.
> >
> > Your VB application is considered "middleware" or a "user aggregator"
for
> > licensing purposes. As such you remove it from consideration entirely.
> >
> > Enterprise vs. Standard Edition SQL choice should be based on which
features
> > you need. IMHO a decent application with 20 or fewer users should work
just
> > fine on Standard Edition.
> >
> > --
> > Geoff N. Hiten
> > Microsoft SQL Server MVP
> > Senior Database Administrator
> > Careerbuilder.com
> >
> > I support the Professional Association for SQL Server
> > www.sqlpass.org
> >
> > "dbelley_office" <dbelley_office@.discussions.microsoft.com> wrote in
message
> > news:F93D8030-77CD-4EDE-87D6-D05BCC44DBF3@.microsoft.com...
> > > Hi,
> > >
> > > I read the licensing page, but still i'm confused ... as always with
> > > licensing stuff.
> > >
> > > I have a VB 6.0 application (.exe) that establish the connection to my
> > > Access database, but we might want to switch to SQL Server2000 in a
near
> > > future.
> > >
> > > Our situation
> > > --
> > > Maximum # of users to use my VB application will be 20. That means I
will
> > > deploy my VB app on 20 computers. BUT my VB application will always
logon
> > to
> > > the database using the same user.
> > >
> > > What would be the best licensing model for me considering all these
facts?
> > > 1- Connection established from a VB application interface.
> > > 2- 20 computers will run the VB application
> > > 3- On the 20 computers running the VB app, the SQL user to establish
the
> > > connection will always be the same. So only 1 user.
> > >
> > > Few more users won't use the VB app and will connect to the database
from
> > > the Entreprise Manager (2-3 users)
> > >
> > > SQL Server...
> > > Entreprise or Standard. I wonder if standard can do the job for us,
it is
> > a
> > > lot cheaper. I think yes. What's the big difference between the two?
We
> > > don't need the super big thing here.
> > >
> > >
> > > Thanks for helping.
> > > Dominic.
> >
> >
> >
Monday, March 12, 2012
HELP ! Production down and backups not restoring properly!
I was mistakenly logged into the wrong server this morning and deleted all
of our product related information!!
I've been doing weekly full backups with hourly log file backups.
I have 2 questions...
1. The most pressing first. My weekly backup happens every Saturday
morning at 2am. My hourly log backups stop between midnight and begin again
at 6:15am Saturday. When I restore the full backup from last saturday it
restores fine. When I go to restore the first log it tells me the log is
too recent and there is an earlier one with LSN###....
I'm really stuck here...there is absolutely no way that there could be an
earlier log. I even tried a RESTORE LOG using the full backup to get the
log from there and it gives the same message.
2. When doing a restore through the SMS after selecting a file off disk you
get the backup sets in that file with checkboxes to select the backupset to
restore. My full backups do not show this. The list is empty so I cannot
go on. The restore seems successful by script. My script statements
originated from the "Generate Script" button when doing backups through the
interface. Am I missing something here? Below is a sample backup
statement:
BACKUP DATABASE [Products]
FILEGROUP = N'PRIMARY'
TO DISK = @.strBackupFile
WITH NOFORMAT, NOINIT,
NAME = @.strBackupFile, SKIP, REWIND, NOUNLOAD, STATS = 10
ANY HELP IS ***GREATLY*** APPRECIATED!!!Actually now I'm seeing after restoring the full backup WITH RECOVERY it
still shows the database in a recovering state and it cannot be accessed!!
How can this happen? What have I done wrong here?
"Tim Greenwood" <tim_greenwood AT yahoo DOT com> wrote in message
news:OaKy0QxEHHA.4404@.TK2MSFTNGP06.phx.gbl...
>I was mistakenly logged into the wrong server this morning and deleted all
>of our product related information!!
> I've been doing weekly full backups with hourly log file backups.
> I have 2 questions...
> 1. The most pressing first. My weekly backup happens every Saturday
> morning at 2am. My hourly log backups stop between midnight and begin
> again at 6:15am Saturday. When I restore the full backup from last
> saturday it restores fine. When I go to restore the first log it tells me
> the log is too recent and there is an earlier one with LSN###....
> I'm really stuck here...there is absolutely no way that there could be an
> earlier log. I even tried a RESTORE LOG using the full backup to get the
> log from there and it gives the same message.
> 2. When doing a restore through the SMS after selecting a file off disk
> you get the backup sets in that file with checkboxes to select the
> backupset to restore. My full backups do not show this. The list is
> empty so I cannot go on. The restore seems successful by script. My
> script statements originated from the "Generate Script" button when doing
> backups through the interface. Am I missing something here? Below is a
> sample backup statement:
> BACKUP DATABASE [Products]
> FILEGROUP = N'PRIMARY'
> TO DISK = @.strBackupFile
> WITH NOFORMAT, NOINIT,
> NAME = @.strBackupFile, SKIP, REWIND, NOUNLOAD, STATS = 10
>
> ANY HELP IS ***GREATLY*** APPRECIATED!!!
>|||And while on the topic of backups, I setup this process based on input from
this group. It just seems that it ends up having an inordinate amount of
files to have to restore to get back online. Wouldn't it be better to just
do differentials hourly instead of log backups? Then in a failure you'd
never have more than 2 files to restore.
Just wondering.
"Tim Greenwood" <tim_greenwood AT yahoo DOT com> wrote in message
news:OaKy0QxEHHA.4404@.TK2MSFTNGP06.phx.gbl...
>I was mistakenly logged into the wrong server this morning and deleted all
>of our product related information!!
> I've been doing weekly full backups with hourly log file backups.
> I have 2 questions...
> 1. The most pressing first. My weekly backup happens every Saturday
> morning at 2am. My hourly log backups stop between midnight and begin
> again at 6:15am Saturday. When I restore the full backup from last
> saturday it restores fine. When I go to restore the first log it tells me
> the log is too recent and there is an earlier one with LSN###....
> I'm really stuck here...there is absolutely no way that there could be an
> earlier log. I even tried a RESTORE LOG using the full backup to get the
> log from there and it gives the same message.
> 2. When doing a restore through the SMS after selecting a file off disk
> you get the backup sets in that file with checkboxes to select the
> backupset to restore. My full backups do not show this. The list is
> empty so I cannot go on. The restore seems successful by script. My
> script statements originated from the "Generate Script" button when doing
> backups through the interface. Am I missing something here? Below is a
> sample backup statement:
> BACKUP DATABASE [Products]
> FILEGROUP = N'PRIMARY'
> TO DISK = @.strBackupFile
> WITH NOFORMAT, NOINIT,
> NAME = @.strBackupFile, SKIP, REWIND, NOUNLOAD, STATS = 10
>
> ANY HELP IS ***GREATLY*** APPRECIATED!!!
>|||> Wouldn't it be better to just do differentials hourly instead of log backu
ps?
You could do that, but log backups has lot of advantages to diff backups. Th
ese includes
Point in time restore.
Ability to backup log if database becomes toast (zero data loss)
Ability to backup log, and restore the most recent db backup and all subsequ
ent log backup sin case
you get a corruption of the database.
Etc.
In short, log backups has so many advantages so you don't want to trade it f
or diff backups just for
convenience. But sometimes you want to do both db, diff *and* log backups.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Tim Greenwood" <tim_greenwood AT yahoo DOT com> wrote in message
news:OnZRT6xEHHA.4740@.TK2MSFTNGP03.phx.gbl...
> And while on the topic of backups, I setup this process based on input fro
m this group. It just
> seems that it ends up having an inordinate amount of files to have to rest
ore to get back online.
> Wouldn't it be better to just do differentials hourly instead of log backu
ps? Then in a failure
> you'd never have more than 2 files to restore.
> Just wondering.
>
> "Tim Greenwood" <tim_greenwood AT yahoo DOT com> wrote in message
> news:OaKy0QxEHHA.4404@.TK2MSFTNGP06.phx.gbl...
>|||> Actually now I'm seeing after restoring the full backup WITH RECOVERY it still shows the d
atabase
> in a recovering state and it cannot be accessed!!
Perhaps just a refresh problem in your GUI?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Tim Greenwood" <tim_greenwood AT yahoo DOT com> wrote in message
news:OppZhXxEHHA.3224@.TK2MSFTNGP04.phx.gbl...
> Actually now I'm seeing after restoring the full backup WITH RECOVERY it s
till shows the database
> in a recovering state and it cannot be accessed!! How can this happen? Wh
at have I done wrong
> here?
>
> "Tim Greenwood" <tim_greenwood AT yahoo DOT com> wrote in message
> news:OaKy0QxEHHA.4404@.TK2MSFTNGP06.phx.gbl...
>|||> 1. The most pressing first. My weekly backup happens every Saturday morning at 2am. My
hourly
> log backups stop between midnight and begin again at 6:15am Saturday. Whe
n I restore the full
> backup from last saturday it restores fine. When I go to restore the firs
t log it tells me the
> log is too recent and there is an earlier one with LSN###....
You need to hunt down that log backup. You can check the backup history tabl
es in the msdb database,
which can give you a clue where it is.
> 2. When doing a restore through the SMS after selecting a file off disk y
ou get the backup sets
> in that file with checkboxes to select the backupset to restore. My full
backups do not show
> this. The list is empty so I cannot go on.
I suggest you read up on the RESTORE command and use RESTORE HEADERONLY and
RESTORE FILELISTONLY so
you can manage a restore when the GUI is acting up on you.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Tim Greenwood" <tim_greenwood AT yahoo DOT com> wrote in message
news:OaKy0QxEHHA.4404@.TK2MSFTNGP06.phx.gbl...
>I was mistakenly logged into the wrong server this morning and deleted all
of our product related
>information!!
> I've been doing weekly full backups with hourly log file backups.
> I have 2 questions...
> 1. The most pressing first. My weekly backup happens every Saturday mor
ning at 2am. My hourly
> log backups stop between midnight and begin again at 6:15am Saturday. Whe
n I restore the full
> backup from last saturday it restores fine. When I go to restore the firs
t log it tells me the
> log is too recent and there is an earlier one with LSN###....
> I'm really stuck here...there is absolutely no way that there could be an
earlier log. I even
> tried a RESTORE LOG using the full backup to get the log from there and it
gives the same message.
> 2. When doing a restore through the SMS after selecting a file off disk y
ou get the backup sets
> in that file with checkboxes to select the backupset to restore. My full
backups do not show
> this. The list is empty so I cannot go on. The restore seems successful
by script. My script
> statements originated from the "Generate Script" button when doing backups
through the interface.
> Am I missing something here? Below is a sample backup statement:
> BACKUP DATABASE [Products]
> FILEGROUP = N'PRIMARY'
> TO DISK = @.strBackupFile
> WITH NOFORMAT, NOINIT,
> NAME = @.strBackupFile, SKIP, REWIND, NOUNLOAD, STATS = 10
>
> ANY HELP IS ***GREATLY*** APPRECIATED!!!
>
of our product related information!!
I've been doing weekly full backups with hourly log file backups.
I have 2 questions...
1. The most pressing first. My weekly backup happens every Saturday
morning at 2am. My hourly log backups stop between midnight and begin again
at 6:15am Saturday. When I restore the full backup from last saturday it
restores fine. When I go to restore the first log it tells me the log is
too recent and there is an earlier one with LSN###....
I'm really stuck here...there is absolutely no way that there could be an
earlier log. I even tried a RESTORE LOG using the full backup to get the
log from there and it gives the same message.
2. When doing a restore through the SMS after selecting a file off disk you
get the backup sets in that file with checkboxes to select the backupset to
restore. My full backups do not show this. The list is empty so I cannot
go on. The restore seems successful by script. My script statements
originated from the "Generate Script" button when doing backups through the
interface. Am I missing something here? Below is a sample backup
statement:
BACKUP DATABASE [Products]
FILEGROUP = N'PRIMARY'
TO DISK = @.strBackupFile
WITH NOFORMAT, NOINIT,
NAME = @.strBackupFile, SKIP, REWIND, NOUNLOAD, STATS = 10
ANY HELP IS ***GREATLY*** APPRECIATED!!!Actually now I'm seeing after restoring the full backup WITH RECOVERY it
still shows the database in a recovering state and it cannot be accessed!!
How can this happen? What have I done wrong here?
"Tim Greenwood" <tim_greenwood AT yahoo DOT com> wrote in message
news:OaKy0QxEHHA.4404@.TK2MSFTNGP06.phx.gbl...
>I was mistakenly logged into the wrong server this morning and deleted all
>of our product related information!!
> I've been doing weekly full backups with hourly log file backups.
> I have 2 questions...
> 1. The most pressing first. My weekly backup happens every Saturday
> morning at 2am. My hourly log backups stop between midnight and begin
> again at 6:15am Saturday. When I restore the full backup from last
> saturday it restores fine. When I go to restore the first log it tells me
> the log is too recent and there is an earlier one with LSN###....
> I'm really stuck here...there is absolutely no way that there could be an
> earlier log. I even tried a RESTORE LOG using the full backup to get the
> log from there and it gives the same message.
> 2. When doing a restore through the SMS after selecting a file off disk
> you get the backup sets in that file with checkboxes to select the
> backupset to restore. My full backups do not show this. The list is
> empty so I cannot go on. The restore seems successful by script. My
> script statements originated from the "Generate Script" button when doing
> backups through the interface. Am I missing something here? Below is a
> sample backup statement:
> BACKUP DATABASE [Products]
> FILEGROUP = N'PRIMARY'
> TO DISK = @.strBackupFile
> WITH NOFORMAT, NOINIT,
> NAME = @.strBackupFile, SKIP, REWIND, NOUNLOAD, STATS = 10
>
> ANY HELP IS ***GREATLY*** APPRECIATED!!!
>|||And while on the topic of backups, I setup this process based on input from
this group. It just seems that it ends up having an inordinate amount of
files to have to restore to get back online. Wouldn't it be better to just
do differentials hourly instead of log backups? Then in a failure you'd
never have more than 2 files to restore.
Just wondering.
"Tim Greenwood" <tim_greenwood AT yahoo DOT com> wrote in message
news:OaKy0QxEHHA.4404@.TK2MSFTNGP06.phx.gbl...
>I was mistakenly logged into the wrong server this morning and deleted all
>of our product related information!!
> I've been doing weekly full backups with hourly log file backups.
> I have 2 questions...
> 1. The most pressing first. My weekly backup happens every Saturday
> morning at 2am. My hourly log backups stop between midnight and begin
> again at 6:15am Saturday. When I restore the full backup from last
> saturday it restores fine. When I go to restore the first log it tells me
> the log is too recent and there is an earlier one with LSN###....
> I'm really stuck here...there is absolutely no way that there could be an
> earlier log. I even tried a RESTORE LOG using the full backup to get the
> log from there and it gives the same message.
> 2. When doing a restore through the SMS after selecting a file off disk
> you get the backup sets in that file with checkboxes to select the
> backupset to restore. My full backups do not show this. The list is
> empty so I cannot go on. The restore seems successful by script. My
> script statements originated from the "Generate Script" button when doing
> backups through the interface. Am I missing something here? Below is a
> sample backup statement:
> BACKUP DATABASE [Products]
> FILEGROUP = N'PRIMARY'
> TO DISK = @.strBackupFile
> WITH NOFORMAT, NOINIT,
> NAME = @.strBackupFile, SKIP, REWIND, NOUNLOAD, STATS = 10
>
> ANY HELP IS ***GREATLY*** APPRECIATED!!!
>|||> Wouldn't it be better to just do differentials hourly instead of log backu
ps?
You could do that, but log backups has lot of advantages to diff backups. Th
ese includes
Point in time restore.
Ability to backup log if database becomes toast (zero data loss)
Ability to backup log, and restore the most recent db backup and all subsequ
ent log backup sin case
you get a corruption of the database.
Etc.
In short, log backups has so many advantages so you don't want to trade it f
or diff backups just for
convenience. But sometimes you want to do both db, diff *and* log backups.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Tim Greenwood" <tim_greenwood AT yahoo DOT com> wrote in message
news:OnZRT6xEHHA.4740@.TK2MSFTNGP03.phx.gbl...
> And while on the topic of backups, I setup this process based on input fro
m this group. It just
> seems that it ends up having an inordinate amount of files to have to rest
ore to get back online.
> Wouldn't it be better to just do differentials hourly instead of log backu
ps? Then in a failure
> you'd never have more than 2 files to restore.
> Just wondering.
>
> "Tim Greenwood" <tim_greenwood AT yahoo DOT com> wrote in message
> news:OaKy0QxEHHA.4404@.TK2MSFTNGP06.phx.gbl...
>|||> Actually now I'm seeing after restoring the full backup WITH RECOVERY it still shows the d
atabase
> in a recovering state and it cannot be accessed!!
Perhaps just a refresh problem in your GUI?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Tim Greenwood" <tim_greenwood AT yahoo DOT com> wrote in message
news:OppZhXxEHHA.3224@.TK2MSFTNGP04.phx.gbl...
> Actually now I'm seeing after restoring the full backup WITH RECOVERY it s
till shows the database
> in a recovering state and it cannot be accessed!! How can this happen? Wh
at have I done wrong
> here?
>
> "Tim Greenwood" <tim_greenwood AT yahoo DOT com> wrote in message
> news:OaKy0QxEHHA.4404@.TK2MSFTNGP06.phx.gbl...
>|||> 1. The most pressing first. My weekly backup happens every Saturday morning at 2am. My
hourly
> log backups stop between midnight and begin again at 6:15am Saturday. Whe
n I restore the full
> backup from last saturday it restores fine. When I go to restore the firs
t log it tells me the
> log is too recent and there is an earlier one with LSN###....
You need to hunt down that log backup. You can check the backup history tabl
es in the msdb database,
which can give you a clue where it is.
> 2. When doing a restore through the SMS after selecting a file off disk y
ou get the backup sets
> in that file with checkboxes to select the backupset to restore. My full
backups do not show
> this. The list is empty so I cannot go on.
I suggest you read up on the RESTORE command and use RESTORE HEADERONLY and
RESTORE FILELISTONLY so
you can manage a restore when the GUI is acting up on you.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Tim Greenwood" <tim_greenwood AT yahoo DOT com> wrote in message
news:OaKy0QxEHHA.4404@.TK2MSFTNGP06.phx.gbl...
>I was mistakenly logged into the wrong server this morning and deleted all
of our product related
>information!!
> I've been doing weekly full backups with hourly log file backups.
> I have 2 questions...
> 1. The most pressing first. My weekly backup happens every Saturday mor
ning at 2am. My hourly
> log backups stop between midnight and begin again at 6:15am Saturday. Whe
n I restore the full
> backup from last saturday it restores fine. When I go to restore the firs
t log it tells me the
> log is too recent and there is an earlier one with LSN###....
> I'm really stuck here...there is absolutely no way that there could be an
earlier log. I even
> tried a RESTORE LOG using the full backup to get the log from there and it
gives the same message.
> 2. When doing a restore through the SMS after selecting a file off disk y
ou get the backup sets
> in that file with checkboxes to select the backupset to restore. My full
backups do not show
> this. The list is empty so I cannot go on. The restore seems successful
by script. My script
> statements originated from the "Generate Script" button when doing backups
through the interface.
> Am I missing something here? Below is a sample backup statement:
> BACKUP DATABASE [Products]
> FILEGROUP = N'PRIMARY'
> TO DISK = @.strBackupFile
> WITH NOFORMAT, NOINIT,
> NAME = @.strBackupFile, SKIP, REWIND, NOUNLOAD, STATS = 10
>
> ANY HELP IS ***GREATLY*** APPRECIATED!!!
>
HELP ! Production down and backups not restoring properly!
I was mistakenly logged into the wrong server this morning and deleted all
of our product related information!!
I've been doing weekly full backups with hourly log file backups.
I have 2 questions...
1. The most pressing first. My weekly backup happens every Saturday
morning at 2am. My hourly log backups stop between midnight and begin again
at 6:15am Saturday. When I restore the full backup from last saturday it
restores fine. When I go to restore the first log it tells me the log is
too recent and there is an earlier one with LSN###....
I'm really stuck here...there is absolutely no way that there could be an
earlier log. I even tried a RESTORE LOG using the full backup to get the
log from there and it gives the same message.
2. When doing a restore through the SMS after selecting a file off disk you
get the backup sets in that file with checkboxes to select the backupset to
restore. My full backups do not show this. The list is empty so I cannot
go on. The restore seems successful by script. My script statements
originated from the "Generate Script" button when doing backups through the
interface. Am I missing something here? Below is a sample backup
statement:
BACKUP DATABASE [Products]
FILEGROUP = N'PRIMARY'
TO DISK = @.strBackupFile
WITH NOFORMAT, NOINIT,
NAME = @.strBackupFile, SKIP, REWIND, NOUNLOAD, STATS = 10
ANY HELP IS ***GREATLY*** APPRECIATED!!!
Actually now I'm seeing after restoring the full backup WITH RECOVERY it
still shows the database in a recovering state and it cannot be accessed!!
How can this happen? What have I done wrong here?
"Tim Greenwood" <tim_greenwood AT yahoo DOT com> wrote in message
news:OaKy0QxEHHA.4404@.TK2MSFTNGP06.phx.gbl...
>I was mistakenly logged into the wrong server this morning and deleted all
>of our product related information!!
> I've been doing weekly full backups with hourly log file backups.
> I have 2 questions...
> 1. The most pressing first. My weekly backup happens every Saturday
> morning at 2am. My hourly log backups stop between midnight and begin
> again at 6:15am Saturday. When I restore the full backup from last
> saturday it restores fine. When I go to restore the first log it tells me
> the log is too recent and there is an earlier one with LSN###....
> I'm really stuck here...there is absolutely no way that there could be an
> earlier log. I even tried a RESTORE LOG using the full backup to get the
> log from there and it gives the same message.
> 2. When doing a restore through the SMS after selecting a file off disk
> you get the backup sets in that file with checkboxes to select the
> backupset to restore. My full backups do not show this. The list is
> empty so I cannot go on. The restore seems successful by script. My
> script statements originated from the "Generate Script" button when doing
> backups through the interface. Am I missing something here? Below is a
> sample backup statement:
> BACKUP DATABASE [Products]
> FILEGROUP = N'PRIMARY'
> TO DISK = @.strBackupFile
> WITH NOFORMAT, NOINIT,
> NAME = @.strBackupFile, SKIP, REWIND, NOUNLOAD, STATS = 10
>
> ANY HELP IS ***GREATLY*** APPRECIATED!!!
>
|||And while on the topic of backups, I setup this process based on input from
this group. It just seems that it ends up having an inordinate amount of
files to have to restore to get back online. Wouldn't it be better to just
do differentials hourly instead of log backups? Then in a failure you'd
never have more than 2 files to restore.
Just wondering.
"Tim Greenwood" <tim_greenwood AT yahoo DOT com> wrote in message
news:OaKy0QxEHHA.4404@.TK2MSFTNGP06.phx.gbl...
>I was mistakenly logged into the wrong server this morning and deleted all
>of our product related information!!
> I've been doing weekly full backups with hourly log file backups.
> I have 2 questions...
> 1. The most pressing first. My weekly backup happens every Saturday
> morning at 2am. My hourly log backups stop between midnight and begin
> again at 6:15am Saturday. When I restore the full backup from last
> saturday it restores fine. When I go to restore the first log it tells me
> the log is too recent and there is an earlier one with LSN###....
> I'm really stuck here...there is absolutely no way that there could be an
> earlier log. I even tried a RESTORE LOG using the full backup to get the
> log from there and it gives the same message.
> 2. When doing a restore through the SMS after selecting a file off disk
> you get the backup sets in that file with checkboxes to select the
> backupset to restore. My full backups do not show this. The list is
> empty so I cannot go on. The restore seems successful by script. My
> script statements originated from the "Generate Script" button when doing
> backups through the interface. Am I missing something here? Below is a
> sample backup statement:
> BACKUP DATABASE [Products]
> FILEGROUP = N'PRIMARY'
> TO DISK = @.strBackupFile
> WITH NOFORMAT, NOINIT,
> NAME = @.strBackupFile, SKIP, REWIND, NOUNLOAD, STATS = 10
>
> ANY HELP IS ***GREATLY*** APPRECIATED!!!
>
of our product related information!!
I've been doing weekly full backups with hourly log file backups.
I have 2 questions...
1. The most pressing first. My weekly backup happens every Saturday
morning at 2am. My hourly log backups stop between midnight and begin again
at 6:15am Saturday. When I restore the full backup from last saturday it
restores fine. When I go to restore the first log it tells me the log is
too recent and there is an earlier one with LSN###....
I'm really stuck here...there is absolutely no way that there could be an
earlier log. I even tried a RESTORE LOG using the full backup to get the
log from there and it gives the same message.
2. When doing a restore through the SMS after selecting a file off disk you
get the backup sets in that file with checkboxes to select the backupset to
restore. My full backups do not show this. The list is empty so I cannot
go on. The restore seems successful by script. My script statements
originated from the "Generate Script" button when doing backups through the
interface. Am I missing something here? Below is a sample backup
statement:
BACKUP DATABASE [Products]
FILEGROUP = N'PRIMARY'
TO DISK = @.strBackupFile
WITH NOFORMAT, NOINIT,
NAME = @.strBackupFile, SKIP, REWIND, NOUNLOAD, STATS = 10
ANY HELP IS ***GREATLY*** APPRECIATED!!!
Actually now I'm seeing after restoring the full backup WITH RECOVERY it
still shows the database in a recovering state and it cannot be accessed!!
How can this happen? What have I done wrong here?
"Tim Greenwood" <tim_greenwood AT yahoo DOT com> wrote in message
news:OaKy0QxEHHA.4404@.TK2MSFTNGP06.phx.gbl...
>I was mistakenly logged into the wrong server this morning and deleted all
>of our product related information!!
> I've been doing weekly full backups with hourly log file backups.
> I have 2 questions...
> 1. The most pressing first. My weekly backup happens every Saturday
> morning at 2am. My hourly log backups stop between midnight and begin
> again at 6:15am Saturday. When I restore the full backup from last
> saturday it restores fine. When I go to restore the first log it tells me
> the log is too recent and there is an earlier one with LSN###....
> I'm really stuck here...there is absolutely no way that there could be an
> earlier log. I even tried a RESTORE LOG using the full backup to get the
> log from there and it gives the same message.
> 2. When doing a restore through the SMS after selecting a file off disk
> you get the backup sets in that file with checkboxes to select the
> backupset to restore. My full backups do not show this. The list is
> empty so I cannot go on. The restore seems successful by script. My
> script statements originated from the "Generate Script" button when doing
> backups through the interface. Am I missing something here? Below is a
> sample backup statement:
> BACKUP DATABASE [Products]
> FILEGROUP = N'PRIMARY'
> TO DISK = @.strBackupFile
> WITH NOFORMAT, NOINIT,
> NAME = @.strBackupFile, SKIP, REWIND, NOUNLOAD, STATS = 10
>
> ANY HELP IS ***GREATLY*** APPRECIATED!!!
>
|||And while on the topic of backups, I setup this process based on input from
this group. It just seems that it ends up having an inordinate amount of
files to have to restore to get back online. Wouldn't it be better to just
do differentials hourly instead of log backups? Then in a failure you'd
never have more than 2 files to restore.
Just wondering.
"Tim Greenwood" <tim_greenwood AT yahoo DOT com> wrote in message
news:OaKy0QxEHHA.4404@.TK2MSFTNGP06.phx.gbl...
>I was mistakenly logged into the wrong server this morning and deleted all
>of our product related information!!
> I've been doing weekly full backups with hourly log file backups.
> I have 2 questions...
> 1. The most pressing first. My weekly backup happens every Saturday
> morning at 2am. My hourly log backups stop between midnight and begin
> again at 6:15am Saturday. When I restore the full backup from last
> saturday it restores fine. When I go to restore the first log it tells me
> the log is too recent and there is an earlier one with LSN###....
> I'm really stuck here...there is absolutely no way that there could be an
> earlier log. I even tried a RESTORE LOG using the full backup to get the
> log from there and it gives the same message.
> 2. When doing a restore through the SMS after selecting a file off disk
> you get the backup sets in that file with checkboxes to select the
> backupset to restore. My full backups do not show this. The list is
> empty so I cannot go on. The restore seems successful by script. My
> script statements originated from the "Generate Script" button when doing
> backups through the interface. Am I missing something here? Below is a
> sample backup statement:
> BACKUP DATABASE [Products]
> FILEGROUP = N'PRIMARY'
> TO DISK = @.strBackupFile
> WITH NOFORMAT, NOINIT,
> NAME = @.strBackupFile, SKIP, REWIND, NOUNLOAD, STATS = 10
>
> ANY HELP IS ***GREATLY*** APPRECIATED!!!
>
HELP ! Production down and backups not restoring properly!
I was mistakenly logged into the wrong server this morning and deleted all
of our product related information!!
I've been doing weekly full backups with hourly log file backups.
I have 2 questions...
1. The most pressing first. My weekly backup happens every Saturday
morning at 2am. My hourly log backups stop between midnight and begin again
at 6:15am Saturday. When I restore the full backup from last saturday it
restores fine. When I go to restore the first log it tells me the log is
too recent and there is an earlier one with LSN###....
I'm really stuck here...there is absolutely no way that there could be an
earlier log. I even tried a RESTORE LOG using the full backup to get the
log from there and it gives the same message.
2. When doing a restore through the SMS after selecting a file off disk you
get the backup sets in that file with checkboxes to select the backupset to
restore. My full backups do not show this. The list is empty so I cannot
go on. The restore seems successful by script. My script statements
originated from the "Generate Script" button when doing backups through the
interface. Am I missing something here? Below is a sample backup
statement:
BACKUP DATABASE [Products]
FILEGROUP = N'PRIMARY'
TO DISK = @.strBackupFile
WITH NOFORMAT, NOINIT,
NAME = @.strBackupFile, SKIP, REWIND, NOUNLOAD, STATS = 10
ANY HELP IS ***GREATLY*** APPRECIATED!!!Actually now I'm seeing after restoring the full backup WITH RECOVERY it
still shows the database in a recovering state and it cannot be accessed!!
How can this happen? What have I done wrong here?
"Tim Greenwood" <tim_greenwood AT yahoo DOT com> wrote in message
news:OaKy0QxEHHA.4404@.TK2MSFTNGP06.phx.gbl...
>I was mistakenly logged into the wrong server this morning and deleted all
>of our product related information!!
> I've been doing weekly full backups with hourly log file backups.
> I have 2 questions...
> 1. The most pressing first. My weekly backup happens every Saturday
> morning at 2am. My hourly log backups stop between midnight and begin
> again at 6:15am Saturday. When I restore the full backup from last
> saturday it restores fine. When I go to restore the first log it tells me
> the log is too recent and there is an earlier one with LSN###....
> I'm really stuck here...there is absolutely no way that there could be an
> earlier log. I even tried a RESTORE LOG using the full backup to get the
> log from there and it gives the same message.
> 2. When doing a restore through the SMS after selecting a file off disk
> you get the backup sets in that file with checkboxes to select the
> backupset to restore. My full backups do not show this. The list is
> empty so I cannot go on. The restore seems successful by script. My
> script statements originated from the "Generate Script" button when doing
> backups through the interface. Am I missing something here? Below is a
> sample backup statement:
> BACKUP DATABASE [Products]
> FILEGROUP = N'PRIMARY'
> TO DISK = @.strBackupFile
> WITH NOFORMAT, NOINIT,
> NAME = @.strBackupFile, SKIP, REWIND, NOUNLOAD, STATS = 10
>
> ANY HELP IS ***GREATLY*** APPRECIATED!!!
>|||And while on the topic of backups, I setup this process based on input from
this group. It just seems that it ends up having an inordinate amount of
files to have to restore to get back online. Wouldn't it be better to just
do differentials hourly instead of log backups? Then in a failure you'd
never have more than 2 files to restore.
Just wondering.
"Tim Greenwood" <tim_greenwood AT yahoo DOT com> wrote in message
news:OaKy0QxEHHA.4404@.TK2MSFTNGP06.phx.gbl...
>I was mistakenly logged into the wrong server this morning and deleted all
>of our product related information!!
> I've been doing weekly full backups with hourly log file backups.
> I have 2 questions...
> 1. The most pressing first. My weekly backup happens every Saturday
> morning at 2am. My hourly log backups stop between midnight and begin
> again at 6:15am Saturday. When I restore the full backup from last
> saturday it restores fine. When I go to restore the first log it tells me
> the log is too recent and there is an earlier one with LSN###....
> I'm really stuck here...there is absolutely no way that there could be an
> earlier log. I even tried a RESTORE LOG using the full backup to get the
> log from there and it gives the same message.
> 2. When doing a restore through the SMS after selecting a file off disk
> you get the backup sets in that file with checkboxes to select the
> backupset to restore. My full backups do not show this. The list is
> empty so I cannot go on. The restore seems successful by script. My
> script statements originated from the "Generate Script" button when doing
> backups through the interface. Am I missing something here? Below is a
> sample backup statement:
> BACKUP DATABASE [Products]
> FILEGROUP = N'PRIMARY'
> TO DISK = @.strBackupFile
> WITH NOFORMAT, NOINIT,
> NAME = @.strBackupFile, SKIP, REWIND, NOUNLOAD, STATS = 10
>
> ANY HELP IS ***GREATLY*** APPRECIATED!!!
>|||> Wouldn't it be better to just do differentials hourly instead of log backups?
You could do that, but log backups has lot of advantages to diff backups. These includes
Point in time restore.
Ability to backup log if database becomes toast (zero data loss)
Ability to backup log, and restore the most recent db backup and all subsequent log backup sin case
you get a corruption of the database.
Etc.
In short, log backups has so many advantages so you don't want to trade it for diff backups just for
convenience. But sometimes you want to do both db, diff *and* log backups.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Tim Greenwood" <tim_greenwood AT yahoo DOT com> wrote in message
news:OnZRT6xEHHA.4740@.TK2MSFTNGP03.phx.gbl...
> And while on the topic of backups, I setup this process based on input from this group. It just
> seems that it ends up having an inordinate amount of files to have to restore to get back online.
> Wouldn't it be better to just do differentials hourly instead of log backups? Then in a failure
> you'd never have more than 2 files to restore.
> Just wondering.
>
> "Tim Greenwood" <tim_greenwood AT yahoo DOT com> wrote in message
> news:OaKy0QxEHHA.4404@.TK2MSFTNGP06.phx.gbl...
>>I was mistakenly logged into the wrong server this morning and deleted all of our product related
>>information!!
>> I've been doing weekly full backups with hourly log file backups.
>> I have 2 questions...
>> 1. The most pressing first. My weekly backup happens every Saturday morning at 2am. My hourly
>> log backups stop between midnight and begin again at 6:15am Saturday. When I restore the full
>> backup from last saturday it restores fine. When I go to restore the first log it tells me the
>> log is too recent and there is an earlier one with LSN###....
>> I'm really stuck here...there is absolutely no way that there could be an earlier log. I even
>> tried a RESTORE LOG using the full backup to get the log from there and it gives the same
>> message.
>> 2. When doing a restore through the SMS after selecting a file off disk you get the backup sets
>> in that file with checkboxes to select the backupset to restore. My full backups do not show
>> this. The list is empty so I cannot go on. The restore seems successful by script. My script
>> statements originated from the "Generate Script" button when doing backups through the interface.
>> Am I missing something here? Below is a sample backup statement:
>> BACKUP DATABASE [Products]
>> FILEGROUP = N'PRIMARY'
>> TO DISK = @.strBackupFile
>> WITH NOFORMAT, NOINIT,
>> NAME = @.strBackupFile, SKIP, REWIND, NOUNLOAD, STATS = 10
>>
>> ANY HELP IS ***GREATLY*** APPRECIATED!!!
>|||> Actually now I'm seeing after restoring the full backup WITH RECOVERY it still shows the database
> in a recovering state and it cannot be accessed!!
Perhaps just a refresh problem in your GUI?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Tim Greenwood" <tim_greenwood AT yahoo DOT com> wrote in message
news:OppZhXxEHHA.3224@.TK2MSFTNGP04.phx.gbl...
> Actually now I'm seeing after restoring the full backup WITH RECOVERY it still shows the database
> in a recovering state and it cannot be accessed!! How can this happen? What have I done wrong
> here?
>
> "Tim Greenwood" <tim_greenwood AT yahoo DOT com> wrote in message
> news:OaKy0QxEHHA.4404@.TK2MSFTNGP06.phx.gbl...
>>I was mistakenly logged into the wrong server this morning and deleted all of our product related
>>information!!
>> I've been doing weekly full backups with hourly log file backups.
>> I have 2 questions...
>> 1. The most pressing first. My weekly backup happens every Saturday morning at 2am. My hourly
>> log backups stop between midnight and begin again at 6:15am Saturday. When I restore the full
>> backup from last saturday it restores fine. When I go to restore the first log it tells me the
>> log is too recent and there is an earlier one with LSN###....
>> I'm really stuck here...there is absolutely no way that there could be an earlier log. I even
>> tried a RESTORE LOG using the full backup to get the log from there and it gives the same
>> message.
>> 2. When doing a restore through the SMS after selecting a file off disk you get the backup sets
>> in that file with checkboxes to select the backupset to restore. My full backups do not show
>> this. The list is empty so I cannot go on. The restore seems successful by script. My script
>> statements originated from the "Generate Script" button when doing backups through the interface.
>> Am I missing something here? Below is a sample backup statement:
>> BACKUP DATABASE [Products]
>> FILEGROUP = N'PRIMARY'
>> TO DISK = @.strBackupFile
>> WITH NOFORMAT, NOINIT,
>> NAME = @.strBackupFile, SKIP, REWIND, NOUNLOAD, STATS = 10
>>
>> ANY HELP IS ***GREATLY*** APPRECIATED!!!
>|||> 1. The most pressing first. My weekly backup happens every Saturday morning at 2am. My hourly
> log backups stop between midnight and begin again at 6:15am Saturday. When I restore the full
> backup from last saturday it restores fine. When I go to restore the first log it tells me the
> log is too recent and there is an earlier one with LSN###....
You need to hunt down that log backup. You can check the backup history tables in the msdb database,
which can give you a clue where it is.
> 2. When doing a restore through the SMS after selecting a file off disk you get the backup sets
> in that file with checkboxes to select the backupset to restore. My full backups do not show
> this. The list is empty so I cannot go on.
I suggest you read up on the RESTORE command and use RESTORE HEADERONLY and RESTORE FILELISTONLY so
you can manage a restore when the GUI is acting up on you.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Tim Greenwood" <tim_greenwood AT yahoo DOT com> wrote in message
news:OaKy0QxEHHA.4404@.TK2MSFTNGP06.phx.gbl...
>I was mistakenly logged into the wrong server this morning and deleted all of our product related
>information!!
> I've been doing weekly full backups with hourly log file backups.
> I have 2 questions...
> 1. The most pressing first. My weekly backup happens every Saturday morning at 2am. My hourly
> log backups stop between midnight and begin again at 6:15am Saturday. When I restore the full
> backup from last saturday it restores fine. When I go to restore the first log it tells me the
> log is too recent and there is an earlier one with LSN###....
> I'm really stuck here...there is absolutely no way that there could be an earlier log. I even
> tried a RESTORE LOG using the full backup to get the log from there and it gives the same message.
> 2. When doing a restore through the SMS after selecting a file off disk you get the backup sets
> in that file with checkboxes to select the backupset to restore. My full backups do not show
> this. The list is empty so I cannot go on. The restore seems successful by script. My script
> statements originated from the "Generate Script" button when doing backups through the interface.
> Am I missing something here? Below is a sample backup statement:
> BACKUP DATABASE [Products]
> FILEGROUP = N'PRIMARY'
> TO DISK = @.strBackupFile
> WITH NOFORMAT, NOINIT,
> NAME = @.strBackupFile, SKIP, REWIND, NOUNLOAD, STATS = 10
>
> ANY HELP IS ***GREATLY*** APPRECIATED!!!
>
of our product related information!!
I've been doing weekly full backups with hourly log file backups.
I have 2 questions...
1. The most pressing first. My weekly backup happens every Saturday
morning at 2am. My hourly log backups stop between midnight and begin again
at 6:15am Saturday. When I restore the full backup from last saturday it
restores fine. When I go to restore the first log it tells me the log is
too recent and there is an earlier one with LSN###....
I'm really stuck here...there is absolutely no way that there could be an
earlier log. I even tried a RESTORE LOG using the full backup to get the
log from there and it gives the same message.
2. When doing a restore through the SMS after selecting a file off disk you
get the backup sets in that file with checkboxes to select the backupset to
restore. My full backups do not show this. The list is empty so I cannot
go on. The restore seems successful by script. My script statements
originated from the "Generate Script" button when doing backups through the
interface. Am I missing something here? Below is a sample backup
statement:
BACKUP DATABASE [Products]
FILEGROUP = N'PRIMARY'
TO DISK = @.strBackupFile
WITH NOFORMAT, NOINIT,
NAME = @.strBackupFile, SKIP, REWIND, NOUNLOAD, STATS = 10
ANY HELP IS ***GREATLY*** APPRECIATED!!!Actually now I'm seeing after restoring the full backup WITH RECOVERY it
still shows the database in a recovering state and it cannot be accessed!!
How can this happen? What have I done wrong here?
"Tim Greenwood" <tim_greenwood AT yahoo DOT com> wrote in message
news:OaKy0QxEHHA.4404@.TK2MSFTNGP06.phx.gbl...
>I was mistakenly logged into the wrong server this morning and deleted all
>of our product related information!!
> I've been doing weekly full backups with hourly log file backups.
> I have 2 questions...
> 1. The most pressing first. My weekly backup happens every Saturday
> morning at 2am. My hourly log backups stop between midnight and begin
> again at 6:15am Saturday. When I restore the full backup from last
> saturday it restores fine. When I go to restore the first log it tells me
> the log is too recent and there is an earlier one with LSN###....
> I'm really stuck here...there is absolutely no way that there could be an
> earlier log. I even tried a RESTORE LOG using the full backup to get the
> log from there and it gives the same message.
> 2. When doing a restore through the SMS after selecting a file off disk
> you get the backup sets in that file with checkboxes to select the
> backupset to restore. My full backups do not show this. The list is
> empty so I cannot go on. The restore seems successful by script. My
> script statements originated from the "Generate Script" button when doing
> backups through the interface. Am I missing something here? Below is a
> sample backup statement:
> BACKUP DATABASE [Products]
> FILEGROUP = N'PRIMARY'
> TO DISK = @.strBackupFile
> WITH NOFORMAT, NOINIT,
> NAME = @.strBackupFile, SKIP, REWIND, NOUNLOAD, STATS = 10
>
> ANY HELP IS ***GREATLY*** APPRECIATED!!!
>|||And while on the topic of backups, I setup this process based on input from
this group. It just seems that it ends up having an inordinate amount of
files to have to restore to get back online. Wouldn't it be better to just
do differentials hourly instead of log backups? Then in a failure you'd
never have more than 2 files to restore.
Just wondering.
"Tim Greenwood" <tim_greenwood AT yahoo DOT com> wrote in message
news:OaKy0QxEHHA.4404@.TK2MSFTNGP06.phx.gbl...
>I was mistakenly logged into the wrong server this morning and deleted all
>of our product related information!!
> I've been doing weekly full backups with hourly log file backups.
> I have 2 questions...
> 1. The most pressing first. My weekly backup happens every Saturday
> morning at 2am. My hourly log backups stop between midnight and begin
> again at 6:15am Saturday. When I restore the full backup from last
> saturday it restores fine. When I go to restore the first log it tells me
> the log is too recent and there is an earlier one with LSN###....
> I'm really stuck here...there is absolutely no way that there could be an
> earlier log. I even tried a RESTORE LOG using the full backup to get the
> log from there and it gives the same message.
> 2. When doing a restore through the SMS after selecting a file off disk
> you get the backup sets in that file with checkboxes to select the
> backupset to restore. My full backups do not show this. The list is
> empty so I cannot go on. The restore seems successful by script. My
> script statements originated from the "Generate Script" button when doing
> backups through the interface. Am I missing something here? Below is a
> sample backup statement:
> BACKUP DATABASE [Products]
> FILEGROUP = N'PRIMARY'
> TO DISK = @.strBackupFile
> WITH NOFORMAT, NOINIT,
> NAME = @.strBackupFile, SKIP, REWIND, NOUNLOAD, STATS = 10
>
> ANY HELP IS ***GREATLY*** APPRECIATED!!!
>|||> Wouldn't it be better to just do differentials hourly instead of log backups?
You could do that, but log backups has lot of advantages to diff backups. These includes
Point in time restore.
Ability to backup log if database becomes toast (zero data loss)
Ability to backup log, and restore the most recent db backup and all subsequent log backup sin case
you get a corruption of the database.
Etc.
In short, log backups has so many advantages so you don't want to trade it for diff backups just for
convenience. But sometimes you want to do both db, diff *and* log backups.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Tim Greenwood" <tim_greenwood AT yahoo DOT com> wrote in message
news:OnZRT6xEHHA.4740@.TK2MSFTNGP03.phx.gbl...
> And while on the topic of backups, I setup this process based on input from this group. It just
> seems that it ends up having an inordinate amount of files to have to restore to get back online.
> Wouldn't it be better to just do differentials hourly instead of log backups? Then in a failure
> you'd never have more than 2 files to restore.
> Just wondering.
>
> "Tim Greenwood" <tim_greenwood AT yahoo DOT com> wrote in message
> news:OaKy0QxEHHA.4404@.TK2MSFTNGP06.phx.gbl...
>>I was mistakenly logged into the wrong server this morning and deleted all of our product related
>>information!!
>> I've been doing weekly full backups with hourly log file backups.
>> I have 2 questions...
>> 1. The most pressing first. My weekly backup happens every Saturday morning at 2am. My hourly
>> log backups stop between midnight and begin again at 6:15am Saturday. When I restore the full
>> backup from last saturday it restores fine. When I go to restore the first log it tells me the
>> log is too recent and there is an earlier one with LSN###....
>> I'm really stuck here...there is absolutely no way that there could be an earlier log. I even
>> tried a RESTORE LOG using the full backup to get the log from there and it gives the same
>> message.
>> 2. When doing a restore through the SMS after selecting a file off disk you get the backup sets
>> in that file with checkboxes to select the backupset to restore. My full backups do not show
>> this. The list is empty so I cannot go on. The restore seems successful by script. My script
>> statements originated from the "Generate Script" button when doing backups through the interface.
>> Am I missing something here? Below is a sample backup statement:
>> BACKUP DATABASE [Products]
>> FILEGROUP = N'PRIMARY'
>> TO DISK = @.strBackupFile
>> WITH NOFORMAT, NOINIT,
>> NAME = @.strBackupFile, SKIP, REWIND, NOUNLOAD, STATS = 10
>>
>> ANY HELP IS ***GREATLY*** APPRECIATED!!!
>|||> Actually now I'm seeing after restoring the full backup WITH RECOVERY it still shows the database
> in a recovering state and it cannot be accessed!!
Perhaps just a refresh problem in your GUI?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Tim Greenwood" <tim_greenwood AT yahoo DOT com> wrote in message
news:OppZhXxEHHA.3224@.TK2MSFTNGP04.phx.gbl...
> Actually now I'm seeing after restoring the full backup WITH RECOVERY it still shows the database
> in a recovering state and it cannot be accessed!! How can this happen? What have I done wrong
> here?
>
> "Tim Greenwood" <tim_greenwood AT yahoo DOT com> wrote in message
> news:OaKy0QxEHHA.4404@.TK2MSFTNGP06.phx.gbl...
>>I was mistakenly logged into the wrong server this morning and deleted all of our product related
>>information!!
>> I've been doing weekly full backups with hourly log file backups.
>> I have 2 questions...
>> 1. The most pressing first. My weekly backup happens every Saturday morning at 2am. My hourly
>> log backups stop between midnight and begin again at 6:15am Saturday. When I restore the full
>> backup from last saturday it restores fine. When I go to restore the first log it tells me the
>> log is too recent and there is an earlier one with LSN###....
>> I'm really stuck here...there is absolutely no way that there could be an earlier log. I even
>> tried a RESTORE LOG using the full backup to get the log from there and it gives the same
>> message.
>> 2. When doing a restore through the SMS after selecting a file off disk you get the backup sets
>> in that file with checkboxes to select the backupset to restore. My full backups do not show
>> this. The list is empty so I cannot go on. The restore seems successful by script. My script
>> statements originated from the "Generate Script" button when doing backups through the interface.
>> Am I missing something here? Below is a sample backup statement:
>> BACKUP DATABASE [Products]
>> FILEGROUP = N'PRIMARY'
>> TO DISK = @.strBackupFile
>> WITH NOFORMAT, NOINIT,
>> NAME = @.strBackupFile, SKIP, REWIND, NOUNLOAD, STATS = 10
>>
>> ANY HELP IS ***GREATLY*** APPRECIATED!!!
>|||> 1. The most pressing first. My weekly backup happens every Saturday morning at 2am. My hourly
> log backups stop between midnight and begin again at 6:15am Saturday. When I restore the full
> backup from last saturday it restores fine. When I go to restore the first log it tells me the
> log is too recent and there is an earlier one with LSN###....
You need to hunt down that log backup. You can check the backup history tables in the msdb database,
which can give you a clue where it is.
> 2. When doing a restore through the SMS after selecting a file off disk you get the backup sets
> in that file with checkboxes to select the backupset to restore. My full backups do not show
> this. The list is empty so I cannot go on.
I suggest you read up on the RESTORE command and use RESTORE HEADERONLY and RESTORE FILELISTONLY so
you can manage a restore when the GUI is acting up on you.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Tim Greenwood" <tim_greenwood AT yahoo DOT com> wrote in message
news:OaKy0QxEHHA.4404@.TK2MSFTNGP06.phx.gbl...
>I was mistakenly logged into the wrong server this morning and deleted all of our product related
>information!!
> I've been doing weekly full backups with hourly log file backups.
> I have 2 questions...
> 1. The most pressing first. My weekly backup happens every Saturday morning at 2am. My hourly
> log backups stop between midnight and begin again at 6:15am Saturday. When I restore the full
> backup from last saturday it restores fine. When I go to restore the first log it tells me the
> log is too recent and there is an earlier one with LSN###....
> I'm really stuck here...there is absolutely no way that there could be an earlier log. I even
> tried a RESTORE LOG using the full backup to get the log from there and it gives the same message.
> 2. When doing a restore through the SMS after selecting a file off disk you get the backup sets
> in that file with checkboxes to select the backupset to restore. My full backups do not show
> this. The list is empty so I cannot go on. The restore seems successful by script. My script
> statements originated from the "Generate Script" button when doing backups through the interface.
> Am I missing something here? Below is a sample backup statement:
> BACKUP DATABASE [Products]
> FILEGROUP = N'PRIMARY'
> TO DISK = @.strBackupFile
> WITH NOFORMAT, NOINIT,
> NAME = @.strBackupFile, SKIP, REWIND, NOUNLOAD, STATS = 10
>
> ANY HELP IS ***GREATLY*** APPRECIATED!!!
>
Subscribe to:
Posts (Atom)