Apex SQLlog will also tell you who made the changes.

have a look at the round function and divide by a factor of ten to move the decimal.

though the example you have given show incosistent behaviour where some values are...

yes it is;

http://microsoft-ssis.blogspot.com/2011/08/importing-images-with-ssis.html

524,272 terabytes

so should be enough for most systems.

it's all in here

http://msdn.microsoft.com/en-us/library/ms143432.aspx

to move the decimal place divide or multiple by a factor of 10..

eg

select CAST( round((1029097.95790000/1000),5) as numeric(10,6))

tommey152 (10/31/2011)

---

steveb. (10/31/2011)

---

The precision and scale of your datatype is not large enough to support that number at that accuracy.

Your current dataype can support Five digits in front of...

with a stored procedure that will cause an error.

actually it may not always cause an error but it will not do what the hacker is trying to do.

Try it...

The precision and scale of your datatype is not large enough to support that number at that accuracy.

Your current dataype can support Five digits in front of the decimal and...

in my view, yes that is the best way to access your data. As it will help with security and provide a layer between the data and the application.

One of the best ways to prevent it, is to use stored procedures for data manipulation, and then call these stored procedures from your application/website.

It depends on what level of documentation you require.

There are some tools out there that will create ssis documentation for you, a google search will bring them up, but...

I still think a staging table and a Merge is your best bet for performance when it comes to upserts, but if you can let us know a bit...

I dont think that you can call the procedure in that way with a object, you really need to call the procedure with a single value for each parameter.

What...

you are trying to create a table that already exists ('shift')

either check the table exists first, and drop the table before the create script, or bypass the create script all...

The N is not specific to restores, it is the way of telling sql server that the string value could be unicode.

The stats is a percentage showing how often...