Viewing 15 posts - 12,151 through 12,165 (of 13,460 total)
Similar to what someone else posted, this procedure "UGLYSEARCH" is not for use on a production box...if you have a database with 50K columns that are varchar, etc, this is...
Lowell
January 22, 2008 at 11:23 am
sp_executesql is probably being used after building a dynamic sql string...
the inherent problem with that is you could execute a command which makes data changes, but makes so many changes...
Lowell
January 22, 2008 at 11:16 am
you could try the stored proc sp_fkeys [tablename]
that will list all the tables that reference any column in the selected table via a foreign key reference...
if you ment a GUI...
Lowell
January 18, 2008 at 10:14 am
doesn't matter which version of SQL; the script at that link is 2000/2005 compatible.
download the script form the link I posted...it's basically CREATE FUNCTION ProperCase AS....
open SQL Query Analyzer,...
Lowell
January 18, 2008 at 10:08 am
well let me be more detailed: only one server can use the actual .mdb and ldb files at any one time. restored databases were just copies of hte current data.
1.first...
Lowell
January 18, 2008 at 8:37 am
no problems at all; we had both servers up and running at the same time for a week; the databases we detatched and reattched were developer databases, so they had...
Lowell
January 18, 2008 at 8:22 am
just to be sure, can you exec sp_help History and also exec sp_help LM_Date1 so we can be sure the columns H.Paid_Date and LM_Date1.Paid_Date are both datetime?
Lowell
January 18, 2008 at 8:09 am
We recently upgraded, but we did not do it the way you described.
we brought up a new server, and made sure it had access to the san.
depending on the database,...
Lowell
January 18, 2008 at 7:53 am
the only way i see that happening is if the columns with the date is being treated as a varchar...but you said you were sure the fields were datetime data...
Lowell
January 18, 2008 at 7:47 am
i think it's because the script was generated in compatibility 90 syntax, but you are creating the table in V80:
i think this part is not 80 compatible on line 35...
Lowell
January 18, 2008 at 7:34 am
Without more details, I'd build a prototype job that looked something like this:
IF EXISTS(SELECT STATUS FROM SOMETABLE WHERE STATUS='READY')
BEGIN
SET XACT_ABORT ON
...
Lowell
January 17, 2008 at 10:17 am
Karthika Raman (1/17/2008)
Lowell
January 17, 2008 at 9:09 am
i put to gether the table and data, but didn't have time to continue; this might help in the analysis:
create table #SpreadSheet(
Zip varchar(9),
City ...
Lowell
January 17, 2008 at 8:38 am
see this page for someone else who had the same issue:
http://www.sqlservercentral.com/Forums/Topic419269-146-3.aspx
Lowell
January 16, 2008 at 8:42 am
there is a function called Propercase in the script contributions section.
with that function installed, you could then simply do an update:
UPDATE SomeTable
SET NameColumn = dbo.Propercase(NameColumn)
Proper Case A String Or...
Lowell
January 16, 2008 at 8:34 am
Viewing 15 posts - 12,151 through 12,165 (of 13,460 total)