I just watched an on demand webcast for SharePoint which uses SQL as the bac
k
end database. The Microsoft presenter talked about using an explorer tool t
o
open sql backup files and extracting data. Does anybody know what tool he i
s
talking about? Supposedly, Microsoft uses this tool to recover a document
that was deleted on a SharePoint site but was in a full sql backup the
previous night. This is their solution to file level recovery. I've got to
have it.
Will RobinsonI've listed three such tools on my link page:
http://www.karaszi.com/SQLServer/links.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"WillAva" <WillAva@.discussions.microsoft.com> wrote in message
news:A561982D-225D-49EE-879B-BAF5D500D52D@.microsoft.com...
>I just watched an on demand webcast for SharePoint which uses SQL as the ba
ck
> end database. The Microsoft presenter talked about using an explorer tool
to
> open sql backup files and extracting data. Does anybody know what tool he
is
> talking about? Supposedly, Microsoft uses this tool to recover a document
> that was deleted on a SharePoint site but was in a full sql backup the
> previous night. This is their solution to file level recovery. I've got
to
> have it.
>
> --
> Will Robinsonsql
Showing posts with label backend. Show all posts
Showing posts with label backend. Show all posts
Thursday, March 22, 2012
Database Explorer or Backup Explorer Tool?
I just watched an on demand webcast for SharePoint which uses SQL as the back
end database. The Microsoft presenter talked about using an explorer tool to
open sql backup files and extracting data. Does anybody know what tool he is
talking about? Supposedly, Microsoft uses this tool to recover a document
that was deleted on a SharePoint site but was in a full sql backup the
previous night. This is their solution to file level recovery. I've got to
have it.
Will Robinson
I've listed three such tools on my link page:
http://www.karaszi.com/SQLServer/links.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"WillAva" <WillAva@.discussions.microsoft.com> wrote in message
news:A561982D-225D-49EE-879B-BAF5D500D52D@.microsoft.com...
>I just watched an on demand webcast for SharePoint which uses SQL as the back
> end database. The Microsoft presenter talked about using an explorer tool to
> open sql backup files and extracting data. Does anybody know what tool he is
> talking about? Supposedly, Microsoft uses this tool to recover a document
> that was deleted on a SharePoint site but was in a full sql backup the
> previous night. This is their solution to file level recovery. I've got to
> have it.
>
> --
> Will Robinson
end database. The Microsoft presenter talked about using an explorer tool to
open sql backup files and extracting data. Does anybody know what tool he is
talking about? Supposedly, Microsoft uses this tool to recover a document
that was deleted on a SharePoint site but was in a full sql backup the
previous night. This is their solution to file level recovery. I've got to
have it.
Will Robinson
I've listed three such tools on my link page:
http://www.karaszi.com/SQLServer/links.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"WillAva" <WillAva@.discussions.microsoft.com> wrote in message
news:A561982D-225D-49EE-879B-BAF5D500D52D@.microsoft.com...
>I just watched an on demand webcast for SharePoint which uses SQL as the back
> end database. The Microsoft presenter talked about using an explorer tool to
> open sql backup files and extracting data. Does anybody know what tool he is
> talking about? Supposedly, Microsoft uses this tool to recover a document
> that was deleted on a SharePoint site but was in a full sql backup the
> previous night. This is their solution to file level recovery. I've got to
> have it.
>
> --
> Will Robinson
Thursday, March 8, 2012
database diagrams
Hello all,
I upsized an access backend to sql 2005. In the process, the relationships were lost. When I go to the database in Sql, right click on database diagrams, all I get is refresh and a link to go to learn about database diagrams. How can I recreate the diagrams?
Thanks
You'd be better asking the question here: http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=84&SiteID=1
-Jamie
Friday, February 17, 2012
Database Creation Help
Hi All,
I am trying to build a prototype in vb with sql server backend, I have a que
stion regarding the database , due to time constraints i am in a dilema whet
her to build a normalized database or to build a denormalized database and n
ormalize it later'
Which will be a good decision?
Thanks for any help
Sudha.If you don't have time to do it right, where are you going to find the time
to do it over? At least Normalize the biggest pieces.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
"sudha" <anonymous@.discussions.microsoft.com> wrote in message
news:47AACA23-7420-4BF2-9B10-5F37F44123C5@.microsoft.com...
question regarding the database , due to time constraints i am in a dilema
whether to build a normalized database or to build a denormalized database
and normalize it later'
er approval for the project .
Thanks.|||Usual industry practice is to throw away the prototype code when you are
building it for production.
If that is what you anticipate, I guess either way is fine.
But if you want to prove your design concept and if that is the reason you
are building a prototype, then I would do it right the first way, which is
normalized way.
Keep in mind in certain hybrid systems of OLTP/OLAP, the data is
denormalized deliberately for optimum performance between OLTP and Reporting
operations.
HTH
Satish Balusa
Corillian Corp.
"sudha" <anonymous@.discussions.microsoft.com> wrote in message
news:47AACA23-7420-4BF2-9B10-5F37F44123C5@.microsoft.com...
question regarding the database , due to time constraints i am in a dilema
whether to build a normalized database or to build a denormalized database
and normalize it later'
sudha
code when you are
fine.
is the reason you
first way, which is
data is
OLTP and Reporting
message
i am in a dilema
denormalized database
I am trying to build a prototype in vb with sql server backend, I have a que
stion regarding the database , due to time constraints i am in a dilema whet
her to build a normalized database or to build a denormalized database and n
ormalize it later'
Which will be a good decision?
Thanks for any help
Sudha.If you don't have time to do it right, where are you going to find the time
to do it over? At least Normalize the biggest pieces.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
"sudha" <anonymous@.discussions.microsoft.com> wrote in message
news:47AACA23-7420-4BF2-9B10-5F37F44123C5@.microsoft.com...
quote:
> Hi All,
> I am trying to build a prototype in vb with sql server backend, I have a
question regarding the database , due to time constraints i am in a dilema
whether to build a normalized database or to build a denormalized database
and normalize it later'
quote:|||I meant total Normalization ofcourse.Apllication comes into picture only aft
> Which will be a good decision?
>
> Thanks for any help
> Sudha.
>
er approval for the project .
Thanks.|||Usual industry practice is to throw away the prototype code when you are
building it for production.
If that is what you anticipate, I guess either way is fine.
But if you want to prove your design concept and if that is the reason you
are building a prototype, then I would do it right the first way, which is
normalized way.
Keep in mind in certain hybrid systems of OLTP/OLAP, the data is
denormalized deliberately for optimum performance between OLTP and Reporting
operations.
HTH
Satish Balusa
Corillian Corp.
"sudha" <anonymous@.discussions.microsoft.com> wrote in message
news:47AACA23-7420-4BF2-9B10-5F37F44123C5@.microsoft.com...
quote:
> Hi All,
> I am trying to build a prototype in vb with sql server backend, I have a
question regarding the database , due to time constraints i am in a dilema
whether to build a normalized database or to build a denormalized database
and normalize it later'
quote:|||Thanks for the advice.
> Which will be a good decision?
>
> Thanks for any help
> Sudha.
>
sudha
quote:
>--Original Message--
>Usual industry practice is to throw away the prototype
code when you are
quote:
>building it for production.
>If that is what you anticipate, I guess either way is
fine.
quote:
>But if you want to prove your design concept and if that
is the reason you
quote:
>are building a prototype, then I would do it right the
first way, which is
quote:
>normalized way.
>Keep in mind in certain hybrid systems of OLTP/OLAP, the
data is
quote:
>denormalized deliberately for optimum performance between
OLTP and Reporting
quote:
>operations.
>--
>HTH
>Satish Balusa
>Corillian Corp.
>
>"sudha" <anonymous@.discussions.microsoft.com> wrote in
message
quote:
>news:47AACA23-7420-4BF2-9B10-5F37F44123C5@.microsoft.com...
backend, I have a[QUOTE]
>question regarding the database , due to time constraints
i am in a dilema
quote:
>whether to build a normalized database or to build a
denormalized database
quote:
>and normalize it later'
>
>.
>
Database Creation Help
Hi All,
I am trying to build a prototype in vb with sql server backend, I have a question regarding the database , due to time constraints i am in a dilema whether to build a normalized database or to build a denormalized database and normalize it later'
Which will be a good decision?
Thanks for any help
Sudha.If you don't have time to do it right, where are you going to find the time
to do it over? At least Normalize the biggest pieces.
--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
"sudha" <anonymous@.discussions.microsoft.com> wrote in message
news:47AACA23-7420-4BF2-9B10-5F37F44123C5@.microsoft.com...
> Hi All,
> I am trying to build a prototype in vb with sql server backend, I have a
question regarding the database , due to time constraints i am in a dilema
whether to build a normalized database or to build a denormalized database
and normalize it later'
> Which will be a good decision?
>
> Thanks for any help
> Sudha.
>|||I meant total Normalization ofcourse.Apllication comes into picture only after approval for the project .
Thanks.|||Usual industry practice is to throw away the prototype code when you are
building it for production.
If that is what you anticipate, I guess either way is fine.
But if you want to prove your design concept and if that is the reason you
are building a prototype, then I would do it right the first way, which is
normalized way.
Keep in mind in certain hybrid systems of OLTP/OLAP, the data is
denormalized deliberately for optimum performance between OLTP and Reporting
operations.
--
HTH
Satish Balusa
Corillian Corp.
"sudha" <anonymous@.discussions.microsoft.com> wrote in message
news:47AACA23-7420-4BF2-9B10-5F37F44123C5@.microsoft.com...
> Hi All,
> I am trying to build a prototype in vb with sql server backend, I have a
question regarding the database , due to time constraints i am in a dilema
whether to build a normalized database or to build a denormalized database
and normalize it later'
> Which will be a good decision?
>
> Thanks for any help
> Sudha.
>|||Thanks for the advice.
sudha
>--Original Message--
>Usual industry practice is to throw away the prototype
code when you are
>building it for production.
>If that is what you anticipate, I guess either way is
fine.
>But if you want to prove your design concept and if that
is the reason you
>are building a prototype, then I would do it right the
first way, which is
>normalized way.
>Keep in mind in certain hybrid systems of OLTP/OLAP, the
data is
>denormalized deliberately for optimum performance between
OLTP and Reporting
>operations.
>--
>HTH
>Satish Balusa
>Corillian Corp.
>
>"sudha" <anonymous@.discussions.microsoft.com> wrote in
message
>news:47AACA23-7420-4BF2-9B10-5F37F44123C5@.microsoft.com...
>> Hi All,
>> I am trying to build a prototype in vb with sql server
backend, I have a
>question regarding the database , due to time constraints
i am in a dilema
>whether to build a normalized database or to build a
denormalized database
>and normalize it later'
>> Which will be a good decision?
>>
>> Thanks for any help
>> Sudha.
>
>.
>
I am trying to build a prototype in vb with sql server backend, I have a question regarding the database , due to time constraints i am in a dilema whether to build a normalized database or to build a denormalized database and normalize it later'
Which will be a good decision?
Thanks for any help
Sudha.If you don't have time to do it right, where are you going to find the time
to do it over? At least Normalize the biggest pieces.
--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
"sudha" <anonymous@.discussions.microsoft.com> wrote in message
news:47AACA23-7420-4BF2-9B10-5F37F44123C5@.microsoft.com...
> Hi All,
> I am trying to build a prototype in vb with sql server backend, I have a
question regarding the database , due to time constraints i am in a dilema
whether to build a normalized database or to build a denormalized database
and normalize it later'
> Which will be a good decision?
>
> Thanks for any help
> Sudha.
>|||I meant total Normalization ofcourse.Apllication comes into picture only after approval for the project .
Thanks.|||Usual industry practice is to throw away the prototype code when you are
building it for production.
If that is what you anticipate, I guess either way is fine.
But if you want to prove your design concept and if that is the reason you
are building a prototype, then I would do it right the first way, which is
normalized way.
Keep in mind in certain hybrid systems of OLTP/OLAP, the data is
denormalized deliberately for optimum performance between OLTP and Reporting
operations.
--
HTH
Satish Balusa
Corillian Corp.
"sudha" <anonymous@.discussions.microsoft.com> wrote in message
news:47AACA23-7420-4BF2-9B10-5F37F44123C5@.microsoft.com...
> Hi All,
> I am trying to build a prototype in vb with sql server backend, I have a
question regarding the database , due to time constraints i am in a dilema
whether to build a normalized database or to build a denormalized database
and normalize it later'
> Which will be a good decision?
>
> Thanks for any help
> Sudha.
>|||Thanks for the advice.
sudha
>--Original Message--
>Usual industry practice is to throw away the prototype
code when you are
>building it for production.
>If that is what you anticipate, I guess either way is
fine.
>But if you want to prove your design concept and if that
is the reason you
>are building a prototype, then I would do it right the
first way, which is
>normalized way.
>Keep in mind in certain hybrid systems of OLTP/OLAP, the
data is
>denormalized deliberately for optimum performance between
OLTP and Reporting
>operations.
>--
>HTH
>Satish Balusa
>Corillian Corp.
>
>"sudha" <anonymous@.discussions.microsoft.com> wrote in
message
>news:47AACA23-7420-4BF2-9B10-5F37F44123C5@.microsoft.com...
>> Hi All,
>> I am trying to build a prototype in vb with sql server
backend, I have a
>question regarding the database , due to time constraints
i am in a dilema
>whether to build a normalized database or to build a
denormalized database
>and normalize it later'
>> Which will be a good decision?
>>
>> Thanks for any help
>> Sudha.
>
>.
>
Subscribe to:
Posts (Atom)