I am try to put together options in regard to creating a test environment for our Dynamics NAV system. The environment will be mainly used to test new releases / changes ahead of applying them to production.The 2 options I am considering are…
1.Create a second Test instance on our Production SQL Server to host a test database
2.Purchase a set of SQL developer licences and having a totally separate server for our test environment.
My preference would be option 2. However I need to build a convincing case that this is the best way forward. I wondered if I could tap into the thoughts of the SQL Central community and see how other approach this.
Sould one has a seperated environment for production and test system? How do you do it on a same server? Install two instance? How do you seperate test DBs from the production DBs? Please advise...Thank you
I must be missing something, and its starting to fusterate me. Bear with me here. I created a site for a ...client I guess you'd call it, and made this really slick newletter generator thing. The people from the web enter in their info, and if they want, they sign up for a newsletter -- all tied into a db, 1 table, 4 stored procedures, REALLY simple stuff. They insisted I used a certain webhost which, on paper, looks like it will fit the bill. I'm starting to question that. On top of the newsletter thing, I created an aspnetdb for the "administration" side of it for her to log into and send out the newsletter so total, there's 2 dbs in the app_data folder. Locally, it works GREAT and on my test box (iis6) that is running 2k5 express. The webhost runs sql2k in (what I consider) a bastardized way. Can't use the management studio, can't use anything except a really weak web-based interface which adds to my fusteration. Anyway, my questions : 1, is there a way to make the mdf files work with sql2k without having to re-do the whole thing and 2, if I have to redo it, does anyone have an example connection string that might help out?
I want to build a SQL testing environment in an active/active setup. Any recommendations on what I could use if I want to set up the most bare-bones system. I want to do it as cheaply as possible.
I am debating whether to go to all the trouble of setting up on-demand Profiler traces on some test servers for the developers here. Really just tracing RPC:Completed and SQL:BatchCompleted, so the developers can at least try to catch a performance problem before going to production. The question I have, though, is just how useful is this sort of information to mid- to low-level (i.e. experience) developers. One of the bigger concerns is over Java applications, which like to hide their queries behind a lot of "sp_cursorfetch" calls.
My question to the forum is if you are a developer, have you ever dreamed of having this sort of information available? How useful is it?
I am going to try to post a poll along with this, but I am not sure it will work..
We have a production database that was generated by a vendor. The vendor wants us to test a new version of their software. This testing process will take several months. The users want the testing to be as real time as possible. I have developed a series of scripts that will back up our databases and ship them over to our test environment on a nightly basis. We also of course have nightly backups. As a general rule, we do full backups once a week and differentials on a nightly basis.
We are a phone company that has transactions being applied to the database 7 X 24.
My question is this: Is there a way (an option or something) that when my backup of the production database which is destined for the test environment runs, I can tell it to not set the flags that indicate a backup has been done. What I want to avoid is the differential backup process from being 'Confused' about what backup it is doing a differential for.
I would appreciate any help or insight you can give me.
So, we are about 3 weeks away from going into production, and somehow we failed to give much thought to deploying our RS project into production.
We have over 110 report models that need to be deployed into production, and until now, we just deploy into our dev and test environments using Visual Studio. But, in our production environment, our deployers will not have Visual Studio.
Is there any simply backup/restore method that can be used to move our test environment into production? Please don't suggest a copy of each file one at a time /sigh.
We will be implementing our first SQL cluster in December. Our current plan calls for a shared development/test database server with one physical server, but two SQL Server instances. Our production environment will be a SQL cluster. Is it necessary to create a clustered test environment for testing patches, hot-fixes, etc...?
Setting up Transaction Replication in test environment. I am willing to bet that most of you take a production backup (if so, how, and using what?), restoring the database to your test environment, then running a snapshot to your subscriber and away you go.
But perhaps you take a backup of your publisher and subscriber, if so, how do you know there are no inconsistences because there were transactions sitting on the distributor?
What do you do if you have additional indexes on the subscriber for reporting, that are not on the publisher?
Here at work we are having issues with getting consistent databases set up with T Rep, missing rows, duplicate keys at subscriber etc. How to avoid these issues.
I need to create a test database on the live server for performance testing.From time to time, as structural modifications are made to the livedatabase, I'd like to be able to delete the test database and replace itwith a new copy of the live database. Is there a simple way to do this witha script or other? Thanks!
I was wondering if anyone has a neat (preferably automated) method of creating small testing databases from large production instances. My requirement would be to copy the schema and a subset of configuration data from a production database into a test database. The subset of data would be a full copy of a subset of tables, rather than a subset of data within one or more tables. There is a mixture of SQL2000 and SQL2005 servers involved in this requirement. I'm familar with the scripting mechanisms of Enterprise Manager and Management studio and DTS packages, sufficent to perform a process like this manually, but want to productionise and schedule this process to be performed automatically. I'm sure this must be a commonly performed task, so I'm interested to know if anyone has a "best practice" for this requirement.
I am attempting to create a Test db from a full backup of the production db. With 2012, I cannot do it the the way i had done it in previous versions (and now i understand why because of Logical names).
The Test db runs in the same instance as Prod db.
I attempted to run this but come up with errors. This is what i executed:
RESTORE DATABASE TEST FROM DISK = 'E:<path>FULL.BAK' WITH REPLACE, RECOVERY, MOVE 'PROD' TO 'E:<path>TEST.MDF';
The errors are all cannot execute due to PROD is in use.
I have finished a change request from our client. I need to update clients' database with the one in developments.Here is the changes i made to database:Added/Changed some tablesAdded/Changed some stored proceduresAdded data to some dictionary tableThe data in clients' current database MUST be kept. So how can I merge the changed information to clients' database?
We are setting up a test lab environment with 100 machines. We want one master testing db that gets replicated to each to run scripted application tests nightly.
My goal is to minimize the amount of work to move this thing to each of the 100 test machines. I am wondering if we need to even have the sql local and invest in a monster db server with 100 copies of the db we restore and each test machine point to their own db on that server, or if I should use db mirroring or something to get the master test db to each of those machines instead.
Now that we have a good programming model in SSIS - the question is whether to write automated unit tests for your packages, and would it generally be a good idea for packages?
Also - if yes to write tests - then where to find more informations regarding How to accomplish that?
hi every one, i need to test SSIS pacakge which will import data from different database where record count is around 5 millions. iam planning to test it through c# code as well as manually also. SSIS source : consist of 7 tables SSIS destination :consist of 7 tables Using c# code iam trying to run ssis package through batch file. i am putting expected rowcount, column count in an excel file and comparing same with destination tables by writing query implementing ADO.Net concept. am i going right way ,can any one suggest best and productive way to test the ssis package . what are the other things i need to test it. do any one can add test cases to it.
S.No
Test Case
1
Verify all the tables have been imported.
2
Verify all the rows in each table have been imported.
3
Verify all the columns specified in source query for each table have been imported
4
Verify all the data has been received without any truncation for each column.
5
Verify the schema at source and destination
6
Verify the time taken /speed for data transfer
7
Fields truncated due to difference in length of the field at destination. Regards Arif shareef
I need to restore test DB from production backup but once it is restored I would need all the permissions of sql logins and windows AD account intact in test Db as it was before.
I am a DBA and my boss recently recommended that we change our QA environment so that we don't have any databases on it unless they are actively being tested. This would be to save hardware costs.
The only issue I can think of at this point is that promotion to our QA environment would take up to 2 hours for some of our larger databases if we have to restore production databases to qa for every QA run.
Is this a good idea? How do you run your QA (full or partial copy of prod)? Any input appreciated.
I work on a company where we today have one SQL Server Standard Edition and Reporting Services (SSRS) and Analysis Services (SSAS) installed on the same server.
Now we want to install SQL Server Enterprise Edition, but still have the Standard Edition installed. We are gonna invest in one more server.
I wonder if its possible to install the database engine for both versions on one server and then install instances of SSRS and SSAS on the other server?
Can Standars Edition have SSRS and SSAS on another server than the Database Engine? And is it different versions of SSRS and SSAS between SQL SE and SQL EE, or does SSRS and SSAS get the SQL EE benefits if the database engine is SQL EE?
I have about 23 SQL servers running 6.5 SP3 or SP5a in a 24 hour environment. Most of the activity takes place between 6am and 11pm, with few transaction after 11pm. What is best to do with the main DB's transaction log, have the truncate at checkpoint option checked OR back up the transaction log a couple times a week? The Database is backed up every 6-8 hours.
I have about 40 DTS packages that I want to run against three different databases on the same server. Can someone suggest an easy way to run these jobs and differentiate each time which SQL or INI file to use.
Jimmy writes "We use a software that stores its database in SQL. We currently have a server box running Windows 2000 Server with SP4 and SQL Server 2005 with SP2 which holds the database. The server is wired in but we have several other stations that connect to the database wirelessly.
The problem is with our wireless stations. When a wireless client travels from one access point to a repeater, it'll drop the connection for that moment. Once it picks up the wireless connection again, it requires closing out of the software and going back into it so it reestablishes the SQL connection to the server.
Is there a solution for a seamless reconnection with SQL for our wireless clients? Is this a problem with our software or SQL? Please advise. Thank you."
Hi Guys, Im new to SQL Server 2005. In our organization, I was tasked to implement and maintain MS SQL 2005 database. We have several system developer and they are using MS SQL 2005 as a backend database.
Currenty, they are responsible for designing their own databases required by their application. My concern is that I want to restrict access to my SQL server that only the DB administrator can access the database server.
My question is that, how they can design their databases without accessing the database server. Is it possible for them to access SQL Server with some restriction? I mean, I want to impose some security measures that they can only access objects within their scope.
Our current scenario is that they have MS SQL Express version installed in their pc and from that terminal they can design and test their application and after everything is in place, Its me who will migrate their respective databases for production in MS SQL 2005 server.
Hoping you can provide me the best alterntive to this query.
Trying to figure out what development enviroment we need in order todo the following:- develop a non-native SQL server stored procedure;- call a web service or java program from the stored procedure;- return static values;- call the stored procedure from a view.How do I get a hold of the right tools and what do I need to put thepieces together?Obviously, I've not used SQL server and I'm looking for the basicstarting point.Thanks!
I'm currently using the setup below for my RDA testing. Is there any problem with this setup?
connected connected Client Apps (SQLCE 3.0) -----------------> Windows Server 2003 (Web server) ----------------> Windows XP (SQL2005)
previously was using windows XP to act as web server and have SQL server reside inside the same machine but having 10 connection limitation from windows xp where only 10 client can connect to the machine. The current setup moves the web server out to windows server 2003 and i believe it solves the 10 concurrent connection limitation but how about the SQL server? is it limited to 10 connection from windows server 2003 also? (Windows XP is my testing server, Windows Server 2003 contains important test data for the whole company) . I tried with concurrent RDA pull for 40 client concurrently with 1 pc having 10 client apps but obtain not really satisfying results. Pulling one table (20Mb) needs 1 to 2 mins through LAN networks but pulling concurrently with 40 clients takes up to 20 - 30 mins.
Now that I've installed SQL 2005 Express Advanced, shouldn't there be a DB Environment I can work with? There must be a configuration mistake because I can't see the "container?" Prior to SP1 I had SQL 2005 Express installed and I could open and use SQL; however, once I loaded SP1 that stopped. I thought if I load the "Advanced" I would be "back in business."
i am working in hospital environment. i am a novice in SQL. i have an urgent issue to answer which is around numbering the order of theatre event for the same patient based on the into theatre time. Patients can go to theatres several times in the single hospitalisation. we need to order as 1, 2, 3 and so on based on the into theatre time which is date/time format. your help is much appreciated. thanks.
I am embarking on a project to upgrade our SQL server environment. I'm curious for some opinions on the relative benefits of Log Shipping versus a Clustered environment and you have any experience that has helped form your opinion on the issue?