Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 1234»»»

Moving Day Expand / Collapse
Author
Message
Posted Wednesday, September 16, 2009 9:23 PM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: Administrators
Last Login: Today @ 10:35 AM
Points: 33,071, Visits: 15,182
Comments posted to this topic are about the item Moving Day






Follow me on Twitter: @way0utwest

Forum Etiquette: How to post data/code on a forum to get the best help
Post #789382
Posted Thursday, September 17, 2009 3:14 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Thursday, October 31, 2013 3:11 AM
Points: 171, Visits: 444
I'd love to see (and please let me know if it already exists!) a way to find out when a table was last selected from. We can set up our own logs for statements which affect the data.

With that we could say "lets delete stuff which hasn't been used for a year".
Post #789476
Posted Thursday, September 17, 2009 5:14 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Thursday, March 27, 2014 6:48 AM
Points: 116, Visits: 128
We just went live this past Monday with a migration from SQL 2000 to SQL 2008. This migration also included new servers, new OS (Win2008), Failover Clustering, Virtual Servers (Hyper V) and even went to the 64 bit SQL Server edition. With so many changes occuring at one time we were reluctant to "Clean House". We wanted to make sure if something went wrong it was with the new technology and not something we did by cleanning house.

As of today, we had very little problems with the move. Everything is working as planned. I am now planning to take the broom out of the closet and try to get rid of things that are no longer needed.
Post #789543
Posted Thursday, September 17, 2009 5:57 AM


SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Thursday, November 18, 2010 5:25 AM
Points: 162, Visits: 694
Ben Moorhouse (9/17/2009)
I'd love to see (and please let me know if it already exists!) a way to find out when a table was last selected from. We can set up our own logs for statements which affect the data.

With that we could say "lets delete stuff which hasn't been used for a year".


There isn't a magical switch, at least not that I'm aware of. But you could create a DDL trigger to capture any changes there, and you could create a trace to capture all of the dml changes to the table. That would get what you want, but it would be a PITA.


As far as Steve's idea of "deprecate that" function, I would love to see that.


A backward approach could be made. All of the procedures we have here include insert statements into a logging table. I guess we could search for rows referencing items from sys.procedures and grab those objects not in the logging table. (Unfortunately, we only keep 45 days worth of data)


Couldn't agree more with the need for housekeeping.


Honor Super Omnia-
Jason Miller
Post #789568
Posted Thursday, September 17, 2009 6:04 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Thursday, October 31, 2013 3:11 AM
Points: 171, Visits: 444
Apologies Jason - I meant that I knew we could log changes to objects and data. It's the ability to log select statements which would be incredibly helpful to me.

Not just for housekeeping either, but for identifying people who write bad/inefficient code.
Post #789571
Posted Thursday, September 17, 2009 6:07 AM


SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Thursday, November 18, 2010 5:25 AM
Points: 162, Visits: 694
Ben Moorhouse (9/17/2009)
Apologies Jason - I meant that I knew we could log changes to objects and data. It's the ability to log select statements which would be incredibly helpful to me.

Not just for housekeeping either, but for identifying people who write bad/inefficient code.


You can capture that as well. We have a trace that runs on our production reporting server to capture every single statement that executes on the machine. Let's just say we had some values changed, and "nobody" did it...




Honor Super Omnia-
Jason Miller
Post #789574
Posted Thursday, September 17, 2009 6:10 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Thursday, October 31, 2013 3:11 AM
Points: 171, Visits: 444
We currently have a database on a shared server with other departments.
We will be moving to our own hardware soon, so that might be something we can do.
Thanks for the pointer!
Post #789576
Posted Thursday, September 17, 2009 7:10 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Monday, June 16, 2014 7:20 PM
Points: 2,897, Visits: 5,978
Jason Miller-476791 (9/17/2009)
As far as Steve's idea of "deprecate that" function, I would love to see that.

A backward approach could be made. All of the procedures we have here include insert statements into a logging table. I guess we could search for rows referencing items from sys.procedures and grab those objects not in the logging table. (Unfortunately, we only keep 45 days worth of data)


Couldn't agree more with the need for housekeeping.


I nominate Steve to open a connect item. I'd be very happy to vote for it as I think this is something that would very, very great to have in a future version.
-Luke.


To help us help you read this

For better help with performance problems please read this
Post #789608
Posted Thursday, September 17, 2009 7:30 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, August 4, 2010 10:23 AM
Points: 4, Visits: 50
We just had a major release and I renamed all the old objects with old_. It felt sooooo good. If no errors in a month, they'll go away permanently.
Post #789626
Posted Thursday, September 17, 2009 7:48 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Friday, March 23, 2012 5:58 AM
Points: 8, Visits: 36
I do something similar, objects which we believe to be no longer in use we rename for example.
tblLoginHistory
becomes
tblLoginHistory_UNUSED090917

Then if something breaks or someone shouts we can quickly and easily rename it back. If 6months passes and it's still named the same then we take a backup and drop it.
Post #789654
« Prev Topic | Next Topic »

Add to briefcase 1234»»»

Permissions Expand / Collapse