microsoft.public.sqlserver.programming | Forum profile

  Alex Kuznetsov (alkuzo@gmail.com) writes: > On Jan 7, 5:19pm, Erland Sommarskog <esq...@sommarskog.se> wrote: >> Oops, trigger no longer working! Test? Why on Earth should one test the >> introduction of a standard error handler? Which might even be added on >> broad scale with some change-replace tool? > > Why? Just because I have unit tests executing...

  You can use WHERE predicates like this: WHERE date_column >= DATEADD(YEAR, DATEDIFF(YEAR, '19000101', CURRENT_TIMESTAMP), '19000101') AND date_column < DATEADD(DAY, (DATEDIFF (DAY, '19000105', CURRENT_TIMESTAMP) / 7) * 7, '19000105') The first filter defines dates greater than or equal to the first of the year (the 1/1/1900 date is used just as reference date for calculations),...

  But this will work if you use integers in the check constraint instead of varchars create table bla (col CHAR(2) NOT NULL CONSTRAINT ck_digits2 CHECK (col between 0 and 99) ) --fine insert bla values ('01') insert bla values ('99') insert bla values ('') insert bla values (' ') --these all fail insert bla values ('1a') insert bla values ('B') select * from bla Denis The...

  >> To CELKO - I agree that there is some sloppiness on my part here but most of what you were talking about has nothing to do with me. The source tables I am using are from an accounting system that was originally written over 15 years ago so it seems they weren't following "best practices" at the time. Even though this system is still updated, they would not risk changing table names or fields...

  DECLARE @now SMALLDATETIME, @fFri SMALLDATETIME, @fdty SMALLDATETIME, @lastFriday SMALLDATETIME; SELECT @now = DATEDIFF(DAY, 0, CURRENT_TIMESTAMP) + 1, @fFri = '20090102', -- pick ANY Friday in the past @fdty = DATEADD(YEAR, DATEDIFF(YEAR, 0, @now), 0), @lastFriday = @fFri + (7*(DATEDIFF (DAY, @fFri, @now)/7)); SELECT [datetime_column] FROM dbo.[table] WHERE [datetime_column] >= @fdty AND [datetime_column] <...

  OK. Now it is working! Thanks for the help. Maybe I edited the constraint incorrectly when I added it. "SQL Menace" wrote: > Did you try the code in my first reply? It works for me > > Here it is again > > create table #bla([myCol] char(2)not null > CONSTRAINT ck_digits > check ([myCol] like '[0-9][0-9]' or [myCol] = '') ) > >...

  On Wed, 7 Jan 2009 14:45:30 -0800, Pelican wrote: >Hugo, > Thanks for your reply. > There is no clustered index for this table. This temp table takes in data >from a text file every 30 minutes by a SQL SSIS package (run by a SQL Server >Agent job scheduler) . That is why I am keeping the table there instead of >creating it inside the query each time. > There must be a way to remove...

  Abba http://msdn.microsoft.com/en-us/library/ms190711.aspx "Abba" <SQL_Help@aaa.com> wrote in message news:%23$Fv3SVcJHA.1336@TK2MSFTNGP02.phx.gbl... > Hello, > > Has anyone tried to import the list of registered servers from a SQL2005 > machine to a SQL2008? I am getting a xml node error. Also tried this > article, but it didnt work. > > TIA, >...

  I have had similar requests in the past. One of the approaches I have taken is to use Profiler to view what is happening in the application when certain requests are made. This is useful if the business are looking for reports based on what they see in the front end. It is especially useful if you have one of those applications I have come across where they don't use the database for much besides storage, so you have no...

  On Jan 7, 5:19pm, Erland Sommarskog <esq...@sommarskog.se> wrote: > Oops, trigger no longer working! Test? Why on Earth should one test the > introduction of a standard error handler? Which might even be added on > broad scale with some change-replace tool? Why? Just because I have unit tests executing every single piece of T- SQl, including triggers, and because in my system they run...