Showing posts with label environment. Show all posts
Showing posts with label environment. Show all posts

Tuesday, March 27, 2012

Advice needed on creating a test environment

I have built a sizable (for me anyway) SQL application for a client on
which they now base their entire business. I need to set up a
parallel installation of the database for development purposes, the
idea being I can make changes to the development version without
impacting day to day operations until it is confirmed that all changes
are working correctly. My problem is this: the application gets
information from their headquarters every night along with information
from employees throughout the day. Every night the system performs an
hour of batch processing on the combined data. In order for this
sandbox to work, I need to be able to import into the test system an
exact copy of the data only on which the various stored procedures are
going to do their work.
It makes sense that the time to copy the data over is after the
poduction system finishes getting its data and before the batch
processing starts.
Is the best way to do this to create a bunch of DTS packages to
replace the development data tables with the production using an
append?
Is it possible to take a backup of prod at the appropriate time and restore
it on your test box?
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
..
"Matthew Speed" <mspeed@.mspeed.net> wrote in message
news:78asg1pda4tvee5ug2kh5o5et09bu8m458@.4ax.com...
I have built a sizable (for me anyway) SQL application for a client on
which they now base their entire business. I need to set up a
parallel installation of the database for development purposes, the
idea being I can make changes to the development version without
impacting day to day operations until it is confirmed that all changes
are working correctly. My problem is this: the application gets
information from their headquarters every night along with information
from employees throughout the day. Every night the system performs an
hour of batch processing on the combined data. In order for this
sandbox to work, I need to be able to import into the test system an
exact copy of the data only on which the various stored procedures are
going to do their work.
It makes sense that the time to copy the data over is after the
poduction system finishes getting its data and before the batch
processing starts.
Is the best way to do this to create a bunch of DTS packages to
replace the development data tables with the production using an
append?
|||On Thu, 25 Aug 2005 21:11:34 -0400, "Tom Moreau"
<tom@.dont.spam.me.cips.ca> wrote:

>Is it possible to take a backup of prod at the appropriate time and restore
>it on your test box?
I don't think I can do that because a lot of my development is on
stored procedures. If I back it up and restore I'd lose my work so I
would have to save off my work, restore the backup and then recreate
my work. Right now I am thinking that my only solution is going to be
using DTS to copy all the data over after it does its nightly
retrieval of data from corporate (it is a moderate amount of data)
|||Hi,
I think in this case you may go for Transactional replication only for
Selected tables.
U can specify the time at which it needs to Copy the data from Production to
Developement.
Any help reply..
Regards,
Herbert
"Matthew Speed" wrote:

> I have built a sizable (for me anyway) SQL application for a client on
> which they now base their entire business. I need to set up a
> parallel installation of the database for development purposes, the
> idea being I can make changes to the development version without
> impacting day to day operations until it is confirmed that all changes
> are working correctly. My problem is this: the application gets
> information from their headquarters every night along with information
> from employees throughout the day. Every night the system performs an
> hour of batch processing on the combined data. In order for this
> sandbox to work, I need to be able to import into the test system an
> exact copy of the data only on which the various stored procedures are
> going to do their work.
> It makes sense that the time to copy the data over is after the
> poduction system finishes getting its data and before the batch
> processing starts.
> Is the best way to do this to create a bunch of DTS packages to
> replace the development data tables with the production using an
> append?
>
|||Why don't you store all your work do disk? I wouldn't dare to work in an environment where my latest
revision is in the database? There are also tools that can compare schemas and create a diff DDL
script based on that. This way, you have your source code in .sql files and after restoring the
backup, you just run that .sql file.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Matthew Speed" <mspeed@.mspeed.net> wrote in message
news:bm4tg15kphl0966uf4ie311ov86q72jgui@.4ax.com...
> On Thu, 25 Aug 2005 21:11:34 -0400, "Tom Moreau"
> <tom@.dont.spam.me.cips.ca> wrote:
>
> I don't think I can do that because a lot of my development is on
> stored procedures. If I back it up and restore I'd lose my work so I
> would have to save off my work, restore the backup and then recreate
> my work. Right now I am thinking that my only solution is going to be
> using DTS to copy all the data over after it does its nightly
> retrieval of data from corporate (it is a moderate amount of data)
|||On Thu, 25 Aug 2005 16:34:37 -0400, Matthew Speed <mspeed@.mspeed.net>
wrote:
>I have built a sizable (for me anyway) SQL application for a client on
>which they now base their entire business. I need to set up a
>parallel installation of the database for development purposes, the
>idea being I can make changes to the development version without
>impacting day to day operations until it is confirmed that all changes
>are working correctly. My problem is this: the application gets
>information from their headquarters every night along with information
>from employees throughout the day. Every night the system performs an
>hour of batch processing on the combined data. In order for this
>sandbox to work, I need to be able to import into the test system an
>exact copy of the data only on which the various stored procedures are
>going to do their work.
>It makes sense that the time to copy the data over is after the
>poduction system finishes getting its data and before the batch
>processing starts.
>Is the best way to do this to create a bunch of DTS packages to
>replace the development data tables with the production using an
>append?
Well, is that the only change made to the production data, appends?
Probably not!
Herbert's suggestion to consider replication is a good one.
But, do you really need up-to-date data every day? Usually there is
development that goes on for some days or weeks (or months or years),
often to a different schema than production is using (!!!), and only
then is even somewhat up-to-date data needed for testing.
It's pretty easy to script out all your SPs, restore a backup of
production onto your test machine, then script the SPs back in. Or
keep the SPs in a separate database.
Or, arrange some DTS logic sufficient to do your updates on demand,
but probably more than just appends.
Lots of ways to go, but frankly, none of them is painless!
J.

Advice needed on creating a test environment

I have built a sizable (for me anyway) SQL application for a client on
which they now base their entire business. I need to set up a
parallel installation of the database for development purposes, the
idea being I can make changes to the development version without
impacting day to day operations until it is confirmed that all changes
are working correctly. My problem is this: the application gets
information from their headquarters every night along with information
from employees throughout the day. Every night the system performs an
hour of batch processing on the combined data. In order for this
sandbox to work, I need to be able to import into the test system an
exact copy of the data only on which the various stored procedures are
going to do their work.
It makes sense that the time to copy the data over is after the
poduction system finishes getting its data and before the batch
processing starts.
Is the best way to do this to create a bunch of DTS packages to
replace the development data tables with the production using an
append?Is it possible to take a backup of prod at the appropriate time and restore
it on your test box?
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
.
"Matthew Speed" <mspeed@.mspeed.net> wrote in message
news:78asg1pda4tvee5ug2kh5o5et09bu8m458@.4ax.com...
I have built a sizable (for me anyway) SQL application for a client on
which they now base their entire business. I need to set up a
parallel installation of the database for development purposes, the
idea being I can make changes to the development version without
impacting day to day operations until it is confirmed that all changes
are working correctly. My problem is this: the application gets
information from their headquarters every night along with information
from employees throughout the day. Every night the system performs an
hour of batch processing on the combined data. In order for this
sandbox to work, I need to be able to import into the test system an
exact copy of the data only on which the various stored procedures are
going to do their work.
It makes sense that the time to copy the data over is after the
poduction system finishes getting its data and before the batch
processing starts.
Is the best way to do this to create a bunch of DTS packages to
replace the development data tables with the production using an
append?|||On Thu, 25 Aug 2005 21:11:34 -0400, "Tom Moreau"
<tom@.dont.spam.me.cips.ca> wrote:
>Is it possible to take a backup of prod at the appropriate time and restore
>it on your test box?
I don't think I can do that because a lot of my development is on
stored procedures. If I back it up and restore I'd lose my work so I
would have to save off my work, restore the backup and then recreate
my work. Right now I am thinking that my only solution is going to be
using DTS to copy all the data over after it does its nightly
retrieval of data from corporate (it is a moderate amount of data)|||Hi,
I think in this case you may go for Transactional replication only for
Selected tables.
U can specify the time at which it needs to Copy the data from Production to
Developement.
Any help reply..
Regards,
--
Herbert
"Matthew Speed" wrote:
> I have built a sizable (for me anyway) SQL application for a client on
> which they now base their entire business. I need to set up a
> parallel installation of the database for development purposes, the
> idea being I can make changes to the development version without
> impacting day to day operations until it is confirmed that all changes
> are working correctly. My problem is this: the application gets
> information from their headquarters every night along with information
> from employees throughout the day. Every night the system performs an
> hour of batch processing on the combined data. In order for this
> sandbox to work, I need to be able to import into the test system an
> exact copy of the data only on which the various stored procedures are
> going to do their work.
> It makes sense that the time to copy the data over is after the
> poduction system finishes getting its data and before the batch
> processing starts.
> Is the best way to do this to create a bunch of DTS packages to
> replace the development data tables with the production using an
> append?
>|||Why don't you store all your work do disk? I wouldn't dare to work in an environment where my latest
revision is in the database? There are also tools that can compare schemas and create a diff DDL
script based on that. This way, you have your source code in .sql files and after restoring the
backup, you just run that .sql file.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Matthew Speed" <mspeed@.mspeed.net> wrote in message
news:bm4tg15kphl0966uf4ie311ov86q72jgui@.4ax.com...
> On Thu, 25 Aug 2005 21:11:34 -0400, "Tom Moreau"
> <tom@.dont.spam.me.cips.ca> wrote:
>>Is it possible to take a backup of prod at the appropriate time and restore
>>it on your test box?
> I don't think I can do that because a lot of my development is on
> stored procedures. If I back it up and restore I'd lose my work so I
> would have to save off my work, restore the backup and then recreate
> my work. Right now I am thinking that my only solution is going to be
> using DTS to copy all the data over after it does its nightly
> retrieval of data from corporate (it is a moderate amount of data)|||On Thu, 25 Aug 2005 16:34:37 -0400, Matthew Speed <mspeed@.mspeed.net>
wrote:
>I have built a sizable (for me anyway) SQL application for a client on
>which they now base their entire business. I need to set up a
>parallel installation of the database for development purposes, the
>idea being I can make changes to the development version without
>impacting day to day operations until it is confirmed that all changes
>are working correctly. My problem is this: the application gets
>information from their headquarters every night along with information
>from employees throughout the day. Every night the system performs an
>hour of batch processing on the combined data. In order for this
>sandbox to work, I need to be able to import into the test system an
>exact copy of the data only on which the various stored procedures are
>going to do their work.
>It makes sense that the time to copy the data over is after the
>poduction system finishes getting its data and before the batch
>processing starts.
>Is the best way to do this to create a bunch of DTS packages to
>replace the development data tables with the production using an
>append?
Well, is that the only change made to the production data, appends?
Probably not!
Herbert's suggestion to consider replication is a good one.
But, do you really need up-to-date data every day? Usually there is
development that goes on for some days or weeks (or months or years),
often to a different schema than production is using (!!!), and only
then is even somewhat up-to-date data needed for testing.
It's pretty easy to script out all your SPs, restore a backup of
production onto your test machine, then script the SPs back in. Or
keep the SPs in a separate database.
Or, arrange some DTS logic sufficient to do your updates on demand,
but probably more than just appends.
Lots of ways to go, but frankly, none of them is painless!
J.

Sunday, February 12, 2012

Administrating SQL

Folks,
I am looking a way to better manage my SQL Server environment. Here are my
requirements
1 I need to know used, free and availabe space
2 Utilization of memory and other SQL Server 2000 related resources whether
on weekly average (for example) it's good
3 System spec that running the server.
I can do some kind of scripting to dump everything on one webpage that list
the above info but i would like to find out whether there is already any tool
availabe to ease my administration.
Protype of the display should be something like this
Srv Name Ver RAM(Threshold 2G) Diskspace(threshold 30%) Total Hits(max 300)
A 80.760 1G(Good) 25G out of 50G
235 (good)
Thank you
rupart
Start with
http://www.sql-server-performance.com
"rupart" <rupart@.discussions.microsoft.com> wrote in message
news:D717B8B5-26B0-4320-BC33-9075FF689AA6@.microsoft.com...
> Folks,
> I am looking a way to better manage my SQL Server environment. Here are my
> requirements
> 1 I need to know used, free and availabe space
> 2 Utilization of memory and other SQL Server 2000 related resources
whether
> on weekly average (for example) it's good
> 3 System spec that running the server.
> I can do some kind of scripting to dump everything on one webpage that
list
> the above info but i would like to find out whether there is already any
tool
> availabe to ease my administration.
> Protype of the display should be something like this
> Srv Name Ver RAM(Threshold 2G) Diskspace(threshold 30%) Total Hits(max
300)
> A 80.760 1G(Good) 25G out of 50G
> 235 (good)
> Thank you

Administrating SQL

Folks,
I am looking a way to better manage my SQL Server environment. Here are my
requirements
1 I need to know used, free and availabe space
2 Utilization of memory and other SQL Server 2000 related resources whether
on weekly average (for example) it's good
3 System spec that running the server.
I can do some kind of scripting to dump everything on one webpage that list
the above info but i would like to find out whether there is already any too
l
availabe to ease my administration.
Protype of the display should be something like this
Srv Name Ver RAM(Threshold 2G) Diskspace(threshold 30%) Total Hits(max 300)
A 80.760 1G(Good) 25G out of 50G
235 (good)
Thank yourupart
Start with
http://www.sql-server-performance.com
"rupart" <rupart@.discussions.microsoft.com> wrote in message
news:D717B8B5-26B0-4320-BC33-9075FF689AA6@.microsoft.com...
> Folks,
> I am looking a way to better manage my SQL Server environment. Here are my
> requirements
> 1 I need to know used, free and availabe space
> 2 Utilization of memory and other SQL Server 2000 related resources
whether
> on weekly average (for example) it's good
> 3 System spec that running the server.
> I can do some kind of scripting to dump everything on one webpage that
list
> the above info but i would like to find out whether there is already any
tool
> availabe to ease my administration.
> Protype of the display should be something like this
> Srv Name Ver RAM(Threshold 2G) Diskspace(threshold 30%) Total Hits(max
300)
> A 80.760 1G(Good) 25G out of 50G
> 235 (good)
> Thank you

Administrating SQL

Folks,
I am looking a way to better manage my SQL Server environment. Here are my
requirements
1 I need to know used, free and availabe space
2 Utilization of memory and other SQL Server 2000 related resources whether
on weekly average (for example) it's good
3 System spec that running the server.
I can do some kind of scripting to dump everything on one webpage that list
the above info but i would like to find out whether there is already any tool
availabe to ease my administration.
Protype of the display should be something like this
Srv Name Ver RAM(Threshold 2G) Diskspace(threshold 30%) Total Hits(max 300)
A 80.760 1G(Good) 25G out of 50G
235 (good)
Thank yourupart
Start with
http://www.sql-server-performance.com
"rupart" <rupart@.discussions.microsoft.com> wrote in message
news:D717B8B5-26B0-4320-BC33-9075FF689AA6@.microsoft.com...
> Folks,
> I am looking a way to better manage my SQL Server environment. Here are my
> requirements
> 1 I need to know used, free and availabe space
> 2 Utilization of memory and other SQL Server 2000 related resources
whether
> on weekly average (for example) it's good
> 3 System spec that running the server.
> I can do some kind of scripting to dump everything on one webpage that
list
> the above info but i would like to find out whether there is already any
tool
> availabe to ease my administration.
> Protype of the display should be something like this
> Srv Name Ver RAM(Threshold 2G) Diskspace(threshold 30%) Total Hits(max
300)
> A 80.760 1G(Good) 25G out of 50G
> 235 (good)
> Thank you

Thursday, February 9, 2012

Admin access to SQL without server/domain admin access

We are using Win2k3 R2 with SQL 2000 in a domain environment.

Is it possible to create a domain group to grant admin level and user level access to SQL2000/2005 without giving users server admin or domain admin access?

It has always been my impression that to have admin access to SQL that you had to at least had admin level access on the server.

Any clarification would be greatly appreciated.

Thanks!

Part of the problem may be from using a more generic phrase like "admin level access to SQL". What that means to you, I'm not sure. That could be interpreted as administering the server from the windows level or it could mean being a member of the sysadmins server role in SQL Server.

But you don't need to be a member of a windows windows administrator group (local administrator on the server or domain administrator in the domain) to be a member of the sysamin server role in SQL Server. A member of the sysadmin role in SQL Server can add other logins to the sysadmin role - and anything thing else they want to do as members of the sysadmins role bypass security checks and can do anything in SQL Server. This is what it sounds like you are asking about.

I have seen some similar confusion coming from this type of scenario:

You have your SQL Server running under a service account and that account is a member of the local administrators group on the server on which SQL Server is running

You are a member of the sysadmin server role in SQL Server

Some of the command you execute as a member of the sysadmin role will execute under the security context of the service account. Being that the service account is a member of the local administrators group, you are executing some of the commands as if you are a member of the local administrators group on that server.

But that scenario doesn't mean you are a member of the local administrators group or that you need to be a member of the local administrators group.

-Sue

Admin a SQLServer environment from an Oracle DBA perspective?

Hey all,

Recently we had a small re-org which combined DBA teams,
specifically Oracle and SqlServer. Just wondering if anyone has
documentation/presentations, etc that show's how to admin a SQLServer
environment from an Oracle DBA perspective?

I guess, something that map's each DB's concepts to each other. As
an Oracle DBA how to troubleshoot/support the environment, etc...

Thanks!

DaveDave wrote:

>Hey all,
> Recently we had a small re-org which combined DBA teams,
>specifically Oracle and SqlServer. Just wondering if anyone has
>documentation/presentations, etc that show's how to admin a SQLServer
>environment from an Oracle DBA perspective?
>I guess, something that map's each DB's concepts to each other. As
>an Oracle DBA how to troubleshoot/support the environment, etc...
>Thanks!
>Dave
>
Get Tom Kyte's book 'Expert one-on-one Oracle".

I won't do what you ask. But the first three chapters will point out to
you in graphic detail
the areas on which you will need to focus.

The two database products are so totally different I can't imagine how
one would try to
administer them together. One has limited row level locking and low
escalation. The other
has no similar concept. One has infinite log files the other does not.
One has a multi-versioning
architecture the other does not. One has autonumbering the other
sequences. One has packages
the other does not. One has ... and on and on and on and on.

One person can manage both. But they need to view them as they are, Each
with its own
concepts and architecture. With more differences than similarities.

--
Daniel Morgan
http://www.outreach.washington.edu/...oad/oad_crs.asp
http://www.outreach.washington.edu/...aoa/aoa_crs.asp
damorgan@.x.washington.edu
(replace 'x' with a 'u' to reply)|||Daniel Morgan <damorgan@.x.washington.edu> wrote in message news:<1068163438.675023@.yasure>...

> Get Tom Kyte's book 'Expert one-on-one Oracle".

Oppps... maybe my post wasn't clear.. Were Oracle DBA's inheriting SQL
Server databases, not the other way around. :)

I've read a "Teach yourself in 24 hours SQL Server" book by Sams but I
need to put together some docs for the rest of our group. I'm just
curious if anyone has done that before? ie, Point out to an Oracle
DBA how to administer a SQL Server environment.

Thanks
Dave|||Dave wrote:

>Daniel Morgan <damorgan@.x.washington.edu> wrote in message news:<1068163438.675023@.yasure>...
>
>>Get Tom Kyte's book 'Expert one-on-one Oracle".
>>
>>
>>
>Oppps... maybe my post wasn't clear.. Were Oracle DBA's inheriting SQL
>Server databases, not the other way around. :)
>I've read a "Teach yourself in 24 hours SQL Server" book by Sams but I
>need to put together some docs for the rest of our group. I'm just
>curious if anyone has done that before? ie, Point out to an Oracle
>DBA how to administer a SQL Server environment.
>Thanks
>Dave
>
I did read your post the other way around. I am not aware of any good
books that approach
the subject from the other standpoint.

Given that SQL Server affeccionados proclaim their product's management
ease ... perhaps
you can just ignore it. ;-)

--
Daniel Morgan
http://www.outreach.washington.edu/...oad/oad_crs.asp
http://www.outreach.washington.edu/...aoa/aoa_crs.asp
damorgan@.x.washington.edu
(replace 'x' with a 'u' to reply)|||The article below explains many of the differences in architecture and
terminology. Although written for SQL 7, it mostly applies to SQL 2000
as well.

http://msdn.microsoft.com/library/d.../oracle2sql.asp

The products are totally different in some areas but similar in others.
In any case, you'll need to wear different DBA hats.

Feel free to post your SQL Server specific questions here or to
microsoft.public.sqlserver.server. Many of us work with Oracle as well
and can assist you in managing your SQL Server databases.

--
Hope this helps.

Dan Guzman
SQL Server MVP

--------
SQL FAQ links (courtesy Neil Pike):

http://www.ntfaq.com/Articles/Index...epartmentID=800
http://www.sqlserverfaq.com
http://www.mssqlserver.com/faq
--------

"Dave" <shoad316@.hotmail.com> wrote in message
news:78cf0572.0311061359.587be850@.posting.google.c om...
> Hey all,
> Recently we had a small re-org which combined DBA teams,
> specifically Oracle and SqlServer. Just wondering if anyone has
> documentation/presentations, etc that show's how to admin a SQLServer
> environment from an Oracle DBA perspective?
> I guess, something that map's each DB's concepts to each other. As
> an Oracle DBA how to troubleshoot/support the environment, etc...
> Thanks!
> Dave